From: git repository hosting Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Sat, 29 Dec 2012 19:55:20 +0100 Message-ID: Subject: osmo-bts.git branch zecke/channel-ho-wip updated. 0.1.0-40-g9f3ff4b Message: 16 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 649c54331bbfae402e91546969251a5b969eee2d (commit) discards e9f803eaa457048d4aaf7ac02a1b5ba8c9ab4071 (commit) discards 9645ab5c502297baa971b822f091b79e0d7a9885 (commit) discards 9de8dd1c29010ba8249661b8c23bd3111de4a273 (commit) discards 17cd344750dc3aed90e20f7f2fd6d4cfc134f4cc (commit) discards 12797ceee7416e7e42bcbc5b8efd190b15089ca7 (commit) discards 55c502a42b294f9605d3836b4fc72378205d6b38 (commit) via 9f3ff4bcecd987f0ec3f24ced27251b04cd857a4 (commit) via 3a4c8ea629c110c198d02a59b6b286f70094bb29 (commit) via 01c260f3deb26c40b835b66eb64b93e06f7ad0a9 (commit) via 70aa5abc646d9b3804a2ff1a1d6b0936a3c9c89d (commit) via 3750891fff0e39f68fa4845983dd5c1259c82b63 (commit) via 2f2a57c3ec8f1a7e93ef9859738819c3d24e6f97 (commit) via 28b10925e655c099134ccb4ba40545e96bc76bb7 (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 (649c54331bbfae402e91546969251a5b969eee2d) \ N -- N -- N (9f3ff4bcecd987f0ec3f24ced27251b04cd857a4) 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=9f3ff4bcecd987f0ec3f24ced27251b04cd857a4 commit 9f3ff4bcecd987f0ec3f24ced27251b04cd857a4 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=3a4c8ea629c110c198d02a59b6b286f70094bb29 commit 3a4c8ea629c110c198d02a59b6b286f70094bb29 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=01c260f3deb26c40b835b66eb64b93e06f7ad0a9 commit 01c260f3deb26c40b835b66eb64b93e06f7ad0a9 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=70aa5abc646d9b3804a2ff1a1d6b0936a3c9c89d commit 70aa5abc646d9b3804a2ff1a1d6b0936a3c9c89d 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. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=3750891fff0e39f68fa4845983dd5c1259c82b63 commit 3750891fff0e39f68fa4845983dd5c1259c82b63 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=2f2a57c3ec8f1a7e93ef9859738819c3d24e6f97 commit 2f2a57c3ec8f1a7e93ef9859738819c3d24e6f97 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=28b10925e655c099134ccb4ba40545e96bc76bb7 commit 28b10925e655c099134ccb4ba40545e96bc76bb7 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. ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-sysmo/femtobts.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)