From: git repository hosting Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Sun, 30 Dec 2012 11:36:48 +0100 Message-ID: Subject: osmo-bts.git branch zecke/channel-ho-wip updated. 0.1.0-41-gfcd2dde Message: 21 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-ho-wip has been updated discards 070eaa1268810a59527cb986f3e77275758800b4 (commit) discards 4680e905da4c4d33b342341f6322954200e552c8 (commit) discards 6dac0806935ba55c10b27afa8e2afa310b7272c6 (commit) discards bdb51c041302a03fd790660448b5840fc7b49129 (commit) discards 8cdce893b15b6cfd8bdb591c576bed6e59bb2ff2 (commit) discards 3338585ebe35b9892b85f6cb9c804b7fb9c549be (commit) discards 3acbe6ccaac8d79e81888fff0175aaad8e3fe234 (commit) discards 19c972aba375def04d8e36447f381e97ca08d398 (commit) discards 2f2a57c3ec8f1a7e93ef9859738819c3d24e6f97 (commit) discards 28b10925e655c099134ccb4ba40545e96bc76bb7 (commit) discards 8947d15ef607695630d0c14c085c3d349f31334e (commit) discards 240b787ecf1903f503946822b4679e1cfc93fa11 (commit) via fcd2dde738b5e7870367783fc27f4e6c7b91526a (commit) via 2469164608cc7dea4134cd258a03e547e2be6d20 (commit) via 30f55f6750f3e783fdcae56b0804a79a807a7408 (commit) via ccc9fd2d80a14bb2d2168e40c836b8c2234a78ec (commit) via cbaa96df75445b5dab54e9c0ed62935cf0ae6a4b (commit) via 52347ada176f0fe29c3b66173d1e9cccf70196a0 (commit) via 169993e5859609ac19b6f3c35b9a82656d53f0bf (commit) via 5047e1470256e5e7a147affe5abd91e13bf066da (commit) via f4aabdc66a577ddc5bf84a2febe94522a43e9024 (commit) via 885b1f8db8bfbb21887dd50980be58fdfc07f66b (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 (070eaa1268810a59527cb986f3e77275758800b4) \ N -- N -- N (fcd2dde738b5e7870367783fc27f4e6c7b91526a) 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=fcd2dde738b5e7870367783fc27f4e6c7b91526a commit fcd2dde738b5e7870367783fc27f4e6c7b91526a Author: Holger Hans Peter Freyther Date: Sat Dec 29 18:10:12 2012 +0100 sysmobts/lchan: Simplify code now that DIR_BOTH is gone http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=2469164608cc7dea4134cd258a03e547e2be6d20 commit 2469164608cc7dea4134cd258a03e547e2be6d20 Author: Holger Hans Peter Freyther Date: Sat Dec 29 18:06:08 2012 +0100 sysmobts/lchan: Add various static and runtime checks for SAPI code http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=30f55f6750f3e783fdcae56b0804a79a807a7408 commit 30f55f6750f3e783fdcae56b0804a79a807a7408 Author: Holger Hans Peter Freyther Date: Sat Dec 29 16:45:29 2012 +0100 sysmobts/lchan: On channel release, release all allocated SAPIs This make sures that everything will be released that was allocated during the lifetime of the channel. The code assumes that all previous requests are handled and no activation request is pending. Make sure to release the SAPIs in the right order. For a TCH/F we will need to release the FACCH before we can release the TCH. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=ccc9fd2d80a14bb2d2168e40c836b8c2234a78ec commit ccc9fd2d80a14bb2d2168e40c836b8c2234a78ec Author: Holger Hans Peter Freyther Date: Sat Dec 29 17:38:50 2012 +0100 sysmobts/lchan: Send a Channel Activate Ack when all SAPIs are established http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=cbaa96df75445b5dab54e9c0ed62935cf0ae6a4b commit cbaa96df75445b5dab54e9c0ed62935cf0ae6a4b Author: Holger Hans Peter Freyther Date: Sat Dec 29 16:51:09 2012 +0100 sysmobts/lchan: Release the lchan when all requests are handled When the lchan is in the release request state and all SAPI requests were handled by the dsp we can send the ACK to the BSC. In case of a single sapi failing we will still need to wait until all the other requests were handled. The rel request code will schedule the release of the required SAPIs and once these requets are handled we are done. We don't need to check if all SAPIs are in the none state. There is no RF Channel Release NACK so we will need to ACK the release and remember that some SAPIs are faulty and prevent the channel from being allocated again. In the future the release code could and should check if any release was scheduled at all. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=52347ada176f0fe29c3b66173d1e9cccf70196a0 commit 52347ada176f0fe29c3b66173d1e9cccf70196a0 Author: Holger Hans Peter Freyther Date: Sat Dec 29 16:22:25 2012 +0100 sysmobts/lchan: Share the SAPI release request code http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=169993e5859609ac19b6f3c35b9a82656d53f0bf commit 169993e5859609ac19b6f3c35b9a82656d53f0bf Author: Holger Hans Peter Freyther Date: Sat Dec 29 16:08:38 2012 +0100 sysmobts: Release the SACCH only when it is allocated Use the sapi_dl and sapi_ul state to release the sacch only when it is allocated and separate the the uplink and downlink direction. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=5047e1470256e5e7a147affe5abd91e13bf066da commit 5047e1470256e5e7a147affe5abd91e13bf066da Author: Holger Hans Peter Freyther Date: Sat Dec 29 14:58:27 2012 +0100 sysmobts: Keep track of the SAPI allocation state for each sapi http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=f4aabdc66a577ddc5bf84a2febe94522a43e9024 commit f4aabdc66a577ddc5bf84a2febe94522a43e9024 Author: Holger Hans Peter Freyther Date: Sat Dec 29 13:45:19 2012 +0100 sysmobts: Move the activate request creation to a separate method Begin to kill the 'BOTH' direction handling as newer firmware releases discourage the usage of them. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=885b1f8db8bfbb21887dd50980be58fdfc07f66b commit 885b1f8db8bfbb21887dd50980be58fdfc07f66b Author: Holger Hans Peter Freyther Date: Sat Dec 29 22:14:08 2012 +0100 sysmobts: Fix the comment referring to the value of the timeout Right now it is 30 seconds and not 10. ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-sysmo/oml.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)