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 "OpenBTS' transceiver retro-fit".
The branch, fairwaves/limesdr-support has been created
at 1f34148bdef5a1c3d0e4174f9ef5e0122d97f1c7 (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-trx/commit/?id=1f34148bdef5a1c3d0e4174f9ef5e0122d97f1c7
commit 1f34148bdef5a1c3d0e4174f9ef5e0122d97f1c7
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date: Sat Jun 18 11:23:31 2016 +0300
A lot of various debug of various levels of usefulness.
http://cgit.osmocom.org/osmo-trx/commit/?id=2b0a9569d05b8d99ba3a41b2c18e81ce0a303d14
commit 2b0a9569d05b8d99ba3a41b2c18e81ce0a303d14
Author: Josh Blum <josh at joshknows.com>
Date: Fri Feb 5 00:52:49 2016 -0800
UHD: Add LimeSDR support.
http://cgit.osmocom.org/osmo-trx/commit/?id=a4f5c2f4c96d8a3ceee12af58485e576a6ccfe3f
commit a4f5c2f4c96d8a3ceee12af58485e576a6ccfe3f
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date: Sat Jun 18 10:38:19 2016 +0300
uhd: Remove explicit check for devices with EDGE support.
Now we already have 4 devices (B200, B210, UmTRX, LimeSDR) and it's getting
crowded. We now have a generic check which complains if a configuration is not
found in the offset table. This should be enough for all practical reasons.
If we really want to complain about EDGE support, then we can just check
'edge' flag and change the log message accordingly. I don't see a real need
for this, though.
http://cgit.osmocom.org/osmo-trx/commit/?id=0a803c82ebeed078c4499e43448e5b2e94f9a641
commit 0a803c82ebeed078c4499e43448e5b2e94f9a641
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date: Sat Jun 18 11:16:54 2016 +0300
radioInterface: Initialize power scale with a meaningful default.
Right now if you forget to send "POWER" control command, osmo-trx
will transmitt zeros. This is counter-intuitive and I've spent several
hours debugging this "issue". The issue may happen easily, because
osmo-bts doesn't send "POWER" command if there is no "power" setting
in the configuration file. Given that "POWER" command actually sets
attenuation, it's percieved as optional and in absence of it should
default to "POWER 0" (no attenuation), which translates to power
scale being 1.0.
http://cgit.osmocom.org/osmo-trx/commit/?id=fa3fb82574e51ccbea64c9a510734065adc7e889
commit fa3fb82574e51ccbea64c9a510734065adc7e889
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date: Sat Jun 18 10:50:11 2016 +0300
uhd: Fix comment.
It's osmo-trx, not OpenBTS anymore.
http://cgit.osmocom.org/osmo-trx/commit/?id=356e891d8b18428ca441b7a324fe9a3e8760c553
commit 356e891d8b18428ca441b7a324fe9a3e8760c553
Author: Alexander Chemeris <Alexander.Chemeris at gmail.com>
Date: Sat Jun 18 10:42:33 2016 +0300
radioDevice: GSMRATE macro must have parentheses around its definition.
So we had the following define:
#define GSMRATE 1625e3/6
Now, I wanted to use it in the following expression:
3.0/GSMRATE
which turns into:
3.0/1625e3/6
while what I really wanted is:
3.0/(1625e3/6) = 3.0/1625e3*6
To avoid this, all macros with calculations must be enclosed in parentheses.
-----------------------------------------------------------------------
hooks/post-receive
--
OpenBTS' transceiver retro-fit