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 "The Open Source GSM Base Band stack". The branch, fixeria/fake_trx has been updated discards 3b4ce09989878f428a23e18f0720f856dbd1db57 (commit) discards 6341203f264f534f62d769c76143469e4619b169 (commit) discards ae648b0af8e05aa7bc9cc4f51e13028356a8bf51 (commit) discards 314719654d7392b2f2bd117a1b639a60d22af6cd (commit) discards 0eb8beba77331f252ea487c9edbeac81fe35b050 (commit) discards b0faaad9176439feb2fe666381e84509989a2e85 (commit) discards 9b87a5c1ac1ebcdb7a144a9a23979b77fb2f67ba (commit) via b9b2051c3162bebc15d7f493ddd9c3b2d84a7494 (commit) via 6cc69c0cdca9c832031810e94b91f1f38b5a52bc (commit) via b131198d6fce8b370ba303fa02659097fffae0c6 (commit) via a57cc2ba187d855eb6237b8a83fcc74063b7cb44 (commit) via a0708987998784a91daece832b29041f967f4a68 (commit) via d75ad5505f0805c36aac57a2c5db06bfa39df6a3 (commit) via 0ba1df5b455fef7b5f4b0d66692887993ac153f7 (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 (3b4ce09989878f428a23e18f0720f856dbd1db57) \ N -- N -- N (b9b2051c3162bebc15d7f493ddd9c3b2d84a7494) 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/osmocom-bb/commit/?id=b9b2051c3162bebc15d7f493ddd9c… commit b9b2051c3162bebc15d7f493ddd9c3b2d84a7494 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 18:48:18 2017 +0700 host/trxcon/scheduler: implement TX queue handling Change-Id: I2b7bae53901156524134c4904ea1179268d85601 http://cgit.osmocom.org/osmocom-bb/commit/?id=6cc69c0cdca9c832031810e94b91f… commit 6cc69c0cdca9c832031810e94b91f1f38b5a52bc Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 18:46:56 2017 +0700 host/trxcon/l1ctl.c: handle L1CTL_RACH_REQ Change-Id: I4c06bcf987120c6271b6e2ad94454fa69689a03e http://cgit.osmocom.org/osmocom-bb/commit/?id=b131198d6fce8b370ba303fa02659… commit b131198d6fce8b370ba303fa02659097fffae0c6 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 17:54:09 2017 +0700 host/trxcon/scheduler: store BSIC in trx_instance We need to know BSIC value, before sending RACH requests. So, let's store it in trx_instance and update as soon as the first SCH burst is received after L1CTL_FBSB_REQ. Change-Id: I49574c3661f79f3b4941db6c651baebab2665c1b http://cgit.osmocom.org/osmocom-bb/commit/?id=a57cc2ba187d855eb6237b8a83fcc… commit a57cc2ba187d855eb6237b8a83fcc74063b7cb44 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 17:58:31 2017 +0700 host/trxcon/scheduler: modify trx_lchan_tx_func definition Initially, it was assumed that TX lchan handler will only compose a burst and return a pointer to the buffer. A burst itself could be sent somewhere outside, e.g. by caller. It would be better to send bursts exactly from handler, because in this case it isn't required to have an external buffer. Change-Id: Ic9dcdd366e68cec38c5840ed8f8cdda8236d67c7 http://cgit.osmocom.org/osmocom-bb/commit/?id=a0708987998784a91daece832b290… commit a0708987998784a91daece832b29041f967f4a68 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 17:49:43 2017 +0700 host/trxcon/trx_if.c: expose the trx_if_tx_burst() Change-Id: Iebd644879e2e9067a94cb638b4ec5b75f806923f http://cgit.osmocom.org/osmocom-bb/commit/?id=d75ad5505f0805c36aac57a2c5db0… commit d75ad5505f0805c36aac57a2c5db06bfa39df6a3 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 17:48:01 2017 +0700 host/trxcon/trx_if.c: use proper names for burst handlers Change-Id: I3d36e6d80fcf6353379aa308415c306e1a256a7d http://cgit.osmocom.org/osmocom-bb/commit/?id=0ba1df5b455fef7b5f4b0d6669288… commit 0ba1df5b455fef7b5f4b0d66692887993ac153f7 Author: Vadim Yanitskiy <axilirator(a)gmail.com> Date: Wed Jul 12 17:40:22 2017 +0700 host/trxcon/trx_if.c: fix compatibility with OsmoTRX For some reasons, OsmoTRX sends 158-byte long sequences on DATA interface, where the latest two bytes aren't used. Change-Id: Ie9295e9b0d8956d9e87e2ced8cca9d5e68040f88 ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- The Open Source GSM Base Band stack