21 Jul
2015
21 Jul
'15
3:27 a.m.
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, achemeris/loopback has been updated
discards 09d39a0337452724da5b4317c2b432c0505bce1f (commit)
discards 7271afbd0d30de95113ff035d6ab1a79399c4c3e (commit)
discards 8f60a1b59dbfb61e396f5acaa9fb6b8083d2ad1a (commit)
discards c3ca46108500d9a8da49043452b103114ca9d741 (commit)
discards 5ac8cc4eeae90d21ff813a7c2c6e6ae06d1c47a1 (commit)
discards e132ad7bb0d70adbc1e2f6b783df008a65c32f23 (commit)
via 9ab991191b901b362bc2bd3f6e78c600000a662d (commit)
via 0b305633d6dad11357d23cf39759693c602a80ec (commit)
via adf26f69751480e3bc0c1e8895188509bd5bd518 (commit)
via ceaf0616d22a764738e76daf9684a0cf846c8745 (commit)
via e6a8c0d3960145ea6c6c4d7546669c73697de350 (commit)
via 4e3bfe14126d016bbdde46b05dfa050b9cf7a0bb (commit)
via 7533cab4bc94e655c78151782be4a4a93e001b30 (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 (09d39a0337452724da5b4317c2b432c0505bce1f)
\
N -- N -- N (9ab991191b901b362bc2bd3f6e78c600000a662d)
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/osmo-bts/commit/?id=9ab991191b901b362bc2bd3f6e78c60…
commit 9ab991191b901b362bc2bd3f6e78c600000a662d
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Sun Jun 14 23:49:16 2015 -0400
HACK: Do not discard GSM-FR frames with bad CRC.
http://cgit.osmocom.org/osmo-bts/commit/?id=0b305633d6dad11357d23cf39759693…
commit 0b305633d6dad11357d23cf39759693c602a80ec
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Wed Jun 10 00:47:13 2015 -0400
trx: Support "bad burst" frames coming from osmo-trx.
Todo: We should actually send command to enable this mode in osmo-trx.
http://cgit.osmocom.org/osmo-bts/commit/?id=adf26f69751480e3bc0c1e889518850…
commit adf26f69751480e3bc0c1e8895188509bd5bd518
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Wed Jun 10 00:45:08 2015 -0400
trx: Process undecodable frames coming from osmo-trx.
The purpose is to support RSSI measurements even when we can't decode a burst.
This commit also cleans up and abstracts some of the code in scheduler.c
http://cgit.osmocom.org/osmo-bts/commit/?id=ceaf0616d22a764738e76daf9684a0c…
commit ceaf0616d22a764738e76daf9684a0cf846c8745
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Fri Jun 5 01:07:21 2015 -0400
DEBUG: Bump log levels for messages useful for LOOPBACK debugging.
http://cgit.osmocom.org/osmo-bts/commit/?id=e6a8c0d3960145ea6c6c4d7546669c7…
commit e6a8c0d3960145ea6c6c4d7546669c73697de350
Author: Alexander Chemeris <Alexander.Chemeris(a)gmail.com>
Date: Fri Jun 5 01:05:59 2015 -0400
trx: Add debug message about a successfully decoded FR frame.
-----------------------------------------------------------------------
Summary of changes:
tests/bursts/Makefile.am | 2 +-
tests/bursts/bursts_test.c | 3 +++
2 files changed, 4 insertions(+), 1 deletion(-)
hooks/post-receive
--
Osmocom BTS-side code (Abis, scheduling, ...)