octasic build failure / header versions

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/OpenBSC@lists.osmocom.org/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Sep 7 11:32:25 UTC 2016


On Wed, Sep 07, 2016 at 12:44:37PM +0200, Neels Hofmeyr wrote:
> (1)
> osmo-bts included a struct member not present anywhere in octphy-2g-headers.
> 
> https://gerrit.osmocom.org/820
> https://gerrit.osmocom.org/821
> 
> On our test setup at sysmocom, I found a version of the headers called
> OCTSDR-2G-02.05.00-B780-DEBUG that includes this struct member, but those
> headers have proprietary licensing. Also, the current version apparently is
> 2.07, while the one with the unknown struct header seems to be older: 2.05. So
> it looks like the usCentreArfcn item has been removed in a newer version, even
> though it looks really useful to me.
> 
> It would be good to resolve this confusion, probably as soon as Max is back
> from vacation (Max is the author of the reverted commits).

I should also mention that in effect, multi-TRX support on octasic is expected
to be broken at this stage.

~Neels

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160907/a4b7581a/attachment.bin>


More information about the OpenBSC mailing list