From: git repository hosting Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Sat, 29 Dec 2012 17:47:38 +0100 Message-ID: Subject: osmo-bts.git branch zecke/channel-ho-wip created. 0.1.0-38-g9645ab5 Message: 12 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 created at 9645ab5c502297baa971b822f091b79e0d7a9885 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=9645ab5c502297baa971b822f091b79e0d7a9885 commit 9645ab5c502297baa971b822f091b79e0d7a9885 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=9de8dd1c29010ba8249661b8c23bd3111de4a273 commit 9de8dd1c29010ba8249661b8c23bd3111de4a273 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=17cd344750dc3aed90e20f7f2fd6d4cfc134f4cc commit 17cd344750dc3aed90e20f7f2fd6d4cfc134f4cc 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=12797ceee7416e7e42bcbc5b8efd190b15089ca7 commit 12797ceee7416e7e42bcbc5b8efd190b15089ca7 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=55c502a42b294f9605d3836b4fc72378205d6b38 commit 55c502a42b294f9605d3836b4fc72378205d6b38 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=8947d15ef607695630d0c14c085c3d349f31334e commit 8947d15ef607695630d0c14c085c3d349f31334e 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=240b787ecf1903f503946822b4679e1cfc93fa11 commit 240b787ecf1903f503946822b4679e1cfc93fa11 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. ----------------------------------------------------------------------- hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)