From: git repository hosting <gitosis@osmocom.org>
Precedence: list
To: osmocom-commitlog@lists.osmocom.org
Date: Wed, 18 Apr 2012 19:58:42 +0200
Message-ID: <E1SKZ9O-0000Bd-DH@calypso.gnumonks.org>
Subject: branch zecke/lchan-fixes updated. 0.0.1-68-gf5832f7
Message: 2

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  2f3ad50c96a258742deffc62f17902e001298776 (commit)
  discards  6ca07e35c85d2939aee79a7b8e08bcb03a728b0e (commit)
  discards  c8cbe4ef386967693b4ed1f44ff37518d072e625 (commit)
  discards  8ffc668b977943c6ac963e7f9f944476600996aa (commit)
  discards  4401417413cea37e36ccea16f9090ea1433489a4 (commit)
  discards  932c806d03a9de0a079c6eb5f782294263c38897 (commit)
  discards  7ca241cd202bee323c700a119a3063186c531b31 (commit)
  discards  4a01fc54dcc0caa3cbd5a36a5a75c6b461edf1dc (commit)
  discards  cd222af632a4f3d6d37352ee5e6d8c539c2b8e95 (commit)
  discards  eb4386835fedff1d09155b3e4bbd19f2d42b9059 (commit)
       via  f5832f7064587fccbe74b27226d331cfa45a9087 (commit)
       via  6693e6f5500f82910335ece3f9563d7b7d6401f7 (commit)
       via  72f0734ddb439067338ccf94c6f58d16429b8faa (commit)
       via  a256a957fa7617897609f9c73b136935b8f65097 (commit)
       via  f5570d8976b24c9141b400b35f18dedda3ed9fb3 (commit)
       via  ea928049ec3850d0e41131ffbb7556724d225288 (commit)
       via  4534ecf888bed7b216a7dece1ec3c873911b3900 (commit)
       via  eb9c39ac274d284fd1af33dec0e95e111a69969f (commit)
       via  165b2fc77e18f3d972650d03b8885f3a3fb42072 (commit)
       via  64deee279f49bceb2b0debbd31d4258983574ca3 (commit)
       via  79080518ed50c5c2af6f124cfe1289ade38633f9 (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 (2f3ad50c96a258742deffc62f17902e001298776)
            \
             N -- N -- N (f5832f7064587fccbe74b27226d331cfa45a9087)

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=f5832f7064587fccbe74b27226d331cfa45a9087

commit f5832f7064587fccbe74b27226d331cfa45a9087
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Wed Apr 18 19:42:21 2012 +0200

    lchan: Separate the Uplink/Downlink in activate/deactivate

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=6693e6f5500f82910335ece3f9563d7b7d6401f7

commit 6693e6f5500f82910335ece3f9563d7b7d6401f7
Author: Holger Hans Peter Freyther <zecke@selfish.org>
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.

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=72f0734ddb439067338ccf94c6f58d16429b8faa

commit 72f0734ddb439067338ccf94c6f58d16429b8faa
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Tue Apr 17 22:06:45 2012 +0200

    WIP: Another hack for the release.. trying to get a stable...

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=a256a957fa7617897609f9c73b136935b8f65097

commit a256a957fa7617897609f9c73b136935b8f65097
Author: Holger Hans Peter Freyther <zecke@selfish.org>
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.
    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=f5570d8976b24c9141b400b35f18dedda3ed9fb3

commit f5570d8976b24c9141b400b35f18dedda3ed9fb3
Author: Holger Hans Peter Freyther <zecke@selfish.org>
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=ea928049ec3850d0e41131ffbb7556724d225288

commit ea928049ec3850d0e41131ffbb7556724d225288
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Mon Apr 16 21:46:19 2012 +0200

    lchan: rsl_tx_chan_nack will re-use the msgb, do not msgb_free
    
    Do not msgb_free the msg as it will be re-used inside the nack
    method and return 1 so the caller does not free the msgb. This
    ownership model needs some consideration but the usage of ref
    counts will not yield good results.

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=4534ecf888bed7b216a7dece1ec3c873911b3900

commit 4534ecf888bed7b216a7dece1ec3c873911b3900
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Mon Apr 16 21:37:10 2012 +0200

    lchan: Fix crashes when the specified lchan can not be found
    
    gsm_lchan_name will crash if the lchan is NULL. Introduce an error_report
    method that will do the right thing in the future and report the error.

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=eb9c39ac274d284fd1af33dec0e95e111a69969f

commit eb9c39ac274d284fd1af33dec0e95e111a69969f
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Mon Apr 16 20:14:38 2012 +0200

    lchan: Fix the state transition in the deactivate handler
    
    If the deactivation is failing the channel needs to be moved into
    and error state, if the deactivation completed the channel needs to
    be set to the none state and set the state to release reqeust on
    the deactivation.

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=165b2fc77e18f3d972650d03b8885f3a3fb42072

commit 165b2fc77e18f3d972650d03b8885f3a3fb42072
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Mon Apr 16 20:07:56 2012 +0200

    lchan: Similar to OpenBSC use a set method to change the state
    
    By making all modifications through lchan_set_state we can easily
    add code to verify the state transition.

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=64deee279f49bceb2b0debbd31d4258983574ca3

commit 64deee279f49bceb2b0debbd31d4258983574ca3
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Mon Apr 16 19:10:44 2012 +0200

    sysmobts: Add an option to query the hardware version.

http://cgit.osmocom.org/cgit/osmo-bts/commit/?id=79080518ed50c5c2af6f124cfe1289ade38633f9

commit 79080518ed50c5c2af6f124cfe1289ade38633f9
Author: Holger Hans Peter Freyther <zecke@selfish.org>
Date:   Mon Apr 16 18:49:11 2012 +0200

    common: Add the copyright text to the vty_app_info
    
    This will make app -V print the copyright information like the other
    applications of our universe. An BTS integration that want to list
    additionaly copyright holders needs to access the vty_app_info and create
    a new copyright string.

-----------------------------------------------------------------------

Summary of changes:
 src/osmo-bts-sysmo/oml.c |   54 +++++++++++++++++++++++++++++-----------------
 1 files changed, 34 insertions(+), 20 deletions(-)


hooks/post-receive
-- 
Osmocom BTS-side code (Abis, scheduling, ...)


