From: git repository hosting Precedence: list To: osmocom-commitlog@lists.osmocom.org Date: Wed, 18 Apr 2012 20:48:33 +0200 Message-ID: Subject: branch zecke/lchan-fixes updated. 0.0.1-67-g7a8e514 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/lchan-fixes has been updated discards f5832f7064587fccbe74b27226d331cfa45a9087 (commit) discards 6693e6f5500f82910335ece3f9563d7b7d6401f7 (commit) discards 72f0734ddb439067338ccf94c6f58d16429b8faa (commit) discards a256a957fa7617897609f9c73b136935b8f65097 (commit) discards f5570d8976b24c9141b400b35f18dedda3ed9fb3 (commit) via 7a8e514d4edb161c99c96a9cde2fb6eac88d3e2f (commit) via 5aac5dec0da31862ce46dbb873895f6010339306 (commit) via 0e293394d608e03cc408390db8a290e6aee5981b (commit) via 1f00d3c198fb401ebad6f264998b33fdd13023cb (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 (f5832f7064587fccbe74b27226d331cfa45a9087) \ N -- N -- N (7a8e514d4edb161c99c96a9cde2fb6eac88d3e2f) 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=7a8e514d4edb161c99c96a9cde2fb6eac88d3e2f commit 7a8e514d4edb161c99c96a9cde2fb6eac88d3e2f Author: Holger Hans Peter Freyther Date: Mon Apr 16 22:15:29 2012 +0200 lchan: Refuse to activate a non-idle lchan. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=5aac5dec0da31862ce46dbb873895f6010339306 commit 5aac5dec0da31862ce46dbb873895f6010339306 Author: Holger Hans Peter Freyther Date: Mon Apr 16 23:09:18 2012 +0200 lchan: Send the ACT ACK/NACK after the Layer1 has handled act/deact Send the RSL ACT ACK/NACK after the Layer1 firmware has acked the activation/deactivation. In case the channel can not be activated we will send a NACK. In case the channel can not be deactivated we will send an ACK and the next time the channel is activated we will send a NACK. The release ack will be sent once the TxDownlink of the TCH/SDCCH is closed. Change the rsl_tx_chan_nack method to create a new msgb to be used by the hardware layer, change the return value to ask the caller to delete the msgb. http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=0e293394d608e03cc408390db8a290e6aee5981b commit 0e293394d608e03cc408390db8a290e6aee5981b Author: Holger Hans Peter Freyther Date: Tue Apr 17 22:06:45 2012 +0200 lchan: Separate the Uplink/Downlink in activate/deactivate http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=1f00d3c198fb401ebad6f264998b33fdd13023cb commit 1f00d3c198fb401ebad6f264998b33fdd13023cb Author: Holger Hans Peter Freyther Date: Wed Apr 18 19:31:42 2012 +0200 lchan: Deactivate the SACCH only once, use the sach_deact flag for that Use the deact_sach (renamed to deact_sacch in master) to remember if the SACCH has been disabled. This should fix the case of lchan errors due releasing the lchan twice. ----------------------------------------------------------------------- Summary of changes: src/common/rsl.c | 2 +- src/osmo-bts-sysmo/oml.c | 8 -------- 2 files changed, 1 insertions(+), 9 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)