From: git repository hosting Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Fri, 25 Jan 2013 21:30:32 +0100 Message-ID: Subject: osmo-bts.git branch zecke/channel-release updated. 0.1.0-71-g0a0e6dc Message: 4 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, zecke/channel-release has been updated discards e69c0956abd94f7c7973add65e611682a6054045 (commit) discards 709098c73c8b844af14820175ad70fa1eb296fb0 (commit) discards 6967510511933f2e1682ed978e893d2ba93398a7 (commit) discards e10df9281fa0c04afab84932f5ac70b8a8a49d03 (commit) discards ff5a1fab8dc3a38130257c751c4d5b9a492b8db3 (commit) discards 64554f0d589b9e57d6b4ec0fcf034f108351f44a (commit) discards 945b3dbaaa4db42e4e5417f1372981e6e9fb56f7 (commit) discards eb95e4535d4606e8e889b67d1d538108b6b0ab45 (commit) discards aab241f28dc1ed01066a71b76a57b61ef43d5111 (commit) discards c9bd31fdd5fc8c85b0e792a06667bf61881bca83 (commit) discards 2a600b751b273a2dd798b0ac1ae8b85a39b06cf6 (commit) discards 1163e109dfac7e5de0498a93167758cd7154d167 (commit) discards 817c95f80c32f24c4c6a768e83ebd801f62e9cf1 (commit) discards c7460351dab1a86484700ea395c686981bd7d23d (commit) discards cf95ad191c42ad5f487d4ad1be411ec0179a83fe (commit) discards d8002eb6c2869612b39f8a8357e7a31665b1bec8 (commit) discards 90409c293f484f4032360c7fa5034f2653319861 (commit) discards bc7af9522f3733683d7c317bdb4ba94ddbc84343 (commit) discards f4010fcd6a0e44d3af972ba5168afe2a809854b8 (commit) discards 1697cd9bb0a522d9cb084041e0f053dd09194869 (commit) discards 662f868be19f8ce062422b4e15f37cd671ba42f7 (commit) via 0a0e6dcb66650e6f14760a7c43d0bf59e92e59fc (commit) via 6f3f9a2ab1ae77a2dc7d290ba825e7af2eeb40da (commit) via 22f646d24d0549a12029fd76a7beb46c39ad6e05 (commit) via 36b7f0800b1dc9815833107d26376cbc428eede6 (commit) via f266b38ced6ede774b0a1d998c81b44947211e50 (commit) via 69221f499fbd30f1f60c60ba2fe08be1066026d7 (commit) via 1050c078ae3bd16e0d491c58fdf3112a8108666c (commit) via 483fb36c9fedd530dcdc640b0645b4264933954e (commit) via 78a6d278499f417d074385590cc69d53da1b39fa (commit) via fb8e1ba71fbe64f0dff6116cf057c4f15513be94 (commit) via bd4105de56f0ebd5a49218576741fda76a58071d (commit) via 7403542a6672d59ee6c91a6b85149a21ca8509e3 (commit) via bef4b895d55d6b0d2e1bf60d92f5e66d9645c2be (commit) via 0d2e5d95697e3cedb1d1a7032fd59bdb2f13befb (commit) via 2cdf0f5f8d4fd68aa2b46faba52d44a5dcd6c7f1 (commit) via 451afe2e6caa1c5896cd9d837fe51225486d9cd9 (commit) via 18d42b6845f22131a1eb31fe7f62cba28d83e9ee (commit) via 78516650d1b5ab536f5ecfb8cc25aec12aa3e0eb (commit) via 5a7eebb8f83d3f08cba76decc75be951304cbeb5 (commit) via 1c69633314768ee3472b2adca6c21dcdf263784e (commit) via 2ad2f88d9d2aa9f44204f494c2fafe3051acd1d0 (commit) via 79cb61a276538bfdc5ee7881393757ff91260a00 (commit) via ff8244751f456777675cbb53fbaeae38cb1ddac1 (commit) via 67b711bbf9f3898ab229d6bcfd98596f132bf425 (commit) via 00111ee41f72a754dca1c57510989f7171aa9996 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (e69c0956abd94f7c7973add65e611682a6054045) \ N -- N -- N (0a0e6dcb66650e6f14760a7c43d0bf59e92e59fc) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=0a0e6dcb66650e6f14760a7c43d0bf59e92e59fc commit 0a0e6dcb66650e6f14760a7c43d0bf59e92e59fc Author: Holger Hans Peter Freyther Date: Fri Jan 25 21:16:41 2013 +0100 WIP.. fix the queueing on release... http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=6f3f9a2ab1ae77a2dc7d290ba825e7af2eeb40da commit 6f3f9a2ab1ae77a2dc7d290ba825e7af2eeb40da Author: Holger Hans Peter Freyther Date: Fri Jan 25 19:17:13 2013 +0100 wip http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=22f646d24d0549a12029fd76a7beb46c39ad6e05 commit 22f646d24d0549a12029fd76a7beb46c39ad6e05 Author: Holger Hans Peter Freyther Date: Fri Jan 25 18:55:50 2013 +0100 sysmobts: Do not re-configure the mode when we are disabling the channel The common/rsl.c is already acking the channel modification and we can simply not queue anything when we are in the process of shutting down the lchan SAPIs. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=36b7f0800b1dc9815833107d26376cbc428eede6 commit 36b7f0800b1dc9815833107d26376cbc428eede6 Author: Holger Hans Peter Freyther Date: Fri Jan 25 18:43:20 2013 +0100 oml: Only shut the bts down once If the shutdown timer is already running do not deactivate the RF and do not close the trx. This is addressing another instance of the following warning: [ERROR] : DeviceMng_ValidateL1Handle() => Invalid layer 1 handle http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=f266b38ced6ede774b0a1d998c81b44947211e50 commit f266b38ced6ede774b0a1d998c81b44947211e50 Author: Holger Hans Peter Freyther Date: Wed Jan 23 17:36:14 2013 +0100 WIP... try to overcome the short coming http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=69221f499fbd30f1f60c60ba2fe08be1066026d7 commit 69221f499fbd30f1f60c60ba2fe08be1066026d7 Author: Holger Hans Peter Freyther Date: Wed Jan 16 14:14:36 2013 +0100 DEBUGGING HELP release... WIP... http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=1050c078ae3bd16e0d491c58fdf3112a8108666c commit 1050c078ae3bd16e0d491c58fdf3112a8108666c Author: Holger Hans Peter Freyther Date: Sun Jan 13 09:47:52 2013 +0100 oml: Use the queue for the release handling of a channel There are three new commands. There are two markers and a deactivate command. The markers are used to wait until all previous commands are executed and then to decide if the SAPI needs to be released at all. When asked to release the SACCH the marker will be queued, then on execution of the marker the SACCH in Up-/Downlink will be released. For the RF Channel Release we use another marker, when the marker is executed we check all the SAPIs we want to release. It is possible that the queue looks like this: (SACCH_REL_MARKER is done) REL_MARKER, SACCH DEACT, SACCH DEACT This could happen if a BSC sends SACCH Deactivate and RF Channel Release at the same time. We deal with issue by changing the SAPI state to the REL_REQ state and check_sapi_release will not ask for another release. So after the execution the queue will look like this: SACCH DEACT, FACCH DEACT, TCHF DEACT.. This code does not check that all allocated SAPIs are released. The lchan_deactivate_sapis could be changed to go through all sapis_dl and sapis_ul to fix that. The normal flow should now be: 1.) lchan_deactivate 2.) Check if the queue is empty then go to 4 3.) REL_MARKER is executed and lchan_deactivate_sapis is called 4.) For all SAPIs to be released, check if they are allocated and then schedule a CMD_DEACTIVATE. If there is an error remember something went wrong but continue. 5.) Once all commands are executed send the channel release ack. For the release markers we need to be careful as they might not schedule any work. E.g. if the BSC sends two SACCH DEACTIVATE the second marker will not generate any release requests and we should proceed with the next command. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=483fb36c9fedd530dcdc640b0645b4264933954e commit 483fb36c9fedd530dcdc640b0645b4264933954e Author: Daniel Willmann Date: Fri Jan 4 00:14:11 2013 +0100 oml: Print out power setting in txpower completion callback http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=78a6d278499f417d074385590cc69d53da1b39fa commit 78a6d278499f417d074385590cc69d53da1b39fa Author: Daniel Willmann Date: Thu Jan 3 23:35:12 2013 +0100 oml: Use sapi command queue for setting the logical channel params http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=fb8e1ba71fbe64f0dff6116cf057c4f15513be94 commit fb8e1ba71fbe64f0dff6116cf057c4f15513be94 Author: Daniel Willmann Date: Thu Jan 3 20:55:12 2013 +0100 oml: Enqueue ciphering message through sapi cmd queue as well http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=bd4105de56f0ebd5a49218576741fda76a58071d commit bd4105de56f0ebd5a49218576741fda76a58071d Author: Daniel Willmann Date: Thu Jan 3 17:37:59 2013 +0100 oml: Introduce a SAPI queue for activation and deactivation of SAPIs Put all SAPI requests into a queue and handle them one after another. Begin with the channel activation. Once the queue is empty the channel activate will be sent. For the BCCH activation we do not want to send a channel activation message and this is why we set the lchan->state to NONE. One change is that we do not attempt to call the ciphering routines on the BCCH anymore. This change is necessary to fix issues with LCHANs staying open and being marked as broken by the BSC and will help in implementing handover support as this requires a re-configuration of the lchan on the fly. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=7403542a6672d59ee6c91a6b85149a21ca8509e3 commit 7403542a6672d59ee6c91a6b85149a21ca8509e3 Author: Holger Hans Peter Freyther Date: Sun Jan 20 11:35:48 2013 +0100 measurement: Add debug helper when we have a report for an inactive channel http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=bef4b895d55d6b0d2e1bf60d92f5e66d9645c2be commit bef4b895d55d6b0d2e1bf60d92f5e66d9645c2be Author: Holger Hans Peter Freyther Date: Fri Jan 25 11:22:25 2013 +0100 tests: Share the stub between the paging and ciphering tests http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=0d2e5d95697e3cedb1d1a7032fd59bdb2f13befb commit 0d2e5d95697e3cedb1d1a7032fd59bdb2f13befb Author: Holger Hans Peter Freyther Date: Thu Jan 24 12:00:14 2013 +0100 sysmobts: Re-load the FPGA image and let some time pass before continuing We are not cleanly shutting down the DSP on exit so let us reset both the DSP and the FPGA. Also let some time pass to allow the DSP to properly initialize itself before starting to use it. This is not a fix but a band-aid for the unclean shutdown. ----------------------------------------------------------------------- Summary of changes: src/common/bts.c | 6 ++++++ src/osmo-bts-sysmo/oml.c | 34 ++++++++++++++++++++++++---------- 2 files changed, 30 insertions(+), 10 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)