This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.
gitosis at osmocom.org gitosis at osmocom.orgThis 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, master has been updated via 037dcfe98197e91b13bbc943d128b136355f05b5 (commit) via 380a2e6d902fbfb00fdba9bd81abc0f0b7b2093b (commit) from ccb11487174545672571515cf98671b0267fa141 (commit) 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/osmo-bts/commit/?id=037dcfe98197e91b13bbc943d128b136355f05b5 commit 037dcfe98197e91b13bbc943d128b136355f05b5 Author: Neels Hofmeyr <neels at hofmeyr.de> Date: Tue Jun 21 21:25:59 2016 +0200 dyn PDCH: lc15: chan_nr_by_sapi(): handle TCH/F_PDCH according to ts->flags Analogous to 0d10f0e482cdd50acc916e75a8b3ba1beb94227c on osmo-bts-sysmo. According to the PDCH Active flag, handle a TS as TCH/F or PDCH. Change-Id: I0c97b360136f76bdae8d70d06af9a31fdf75c1ba http://cgit.osmocom.org/osmo-bts/commit/?id=380a2e6d902fbfb00fdba9bd81abc0f0b7b2093b commit 380a2e6d902fbfb00fdba9bd81abc0f0b7b2093b Author: Neels Hofmeyr <neels at hofmeyr.de> Date: Tue Jun 21 19:47:26 2016 +0200 lc15: add L3 handle to l1prim messages Analogous to 7158c2ed082eaca6063a501e490e8d3c3b181560 in osmo-bts-sysmo. Place a layer 3 handle into GSM L1 messages to better match up confirmations to respective requests. This handle is a uint32_t transparently returned in the confirmation messages, so a match-up is easy to add. So far, a GSM L1 confirmation message received for a preceding L1 Request was matched only by the prim_id. That meant that only one instance of the same primitive could be waiting for a confirmation at any given time, or the responses would get mixed up: the struct wait_l1_conf instances entered into the fl1h->wlc_list queue would be returned to a possibly mismatching confirmation handler. (Seen during testing of dyn pdch switching.) Send the hLayer3 handle out via prim_init(), using new static functions to produce handles on different scopes: * l1p_handle_for_trx() * l1p_handle_for_ts() * l1p_handle_for_lchan() (These could possibly move to a more general .h/.c file later.) Remember the hLayer3 handle in * struct wait_l1_conf. Match the incoming confirmations' and stored hLayer3 handles up in, and remove a now obsolete comment from: * is_prim_compat() Since the hLayer3 members are at different byte offsets in GsmL1_Prim_t.u.*, use large switch statements to set/get the value: * In prim_init(), extend existing switch statement to set in GsmL1_Prim_t. * Add l1p_get_hLayer3() to retrieve from GsmL1_Prim_t (could possibly move to a more general .h/.c file later). Note that some messages are already using the hLayer3 handle, and will overwrite it after calling prim_init(), so those are not affected. Change-Id: I17f95ba744c3e944a2241809106506f8dd1b24f0 ----------------------------------------------------------------------- Summary of changes: src/osmo-bts-litecell15/l1_if.c | 75 +++++++++++++++++++++++++++++++++++--- src/osmo-bts-litecell15/oml.c | 81 ++++++++++++++++++++++++++++++++++++----- 2 files changed, 142 insertions(+), 14 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)