| commit | e4cddb5ef10cb466d0b9a3a172c470629e48b28a | |
| author | Vadim Yanitskiy <axilirator@gmail.com> | |
| Mon, 17 Dec 2018 22:34:18 +0000 (18 05:34 +0700) | ||
| committer | Vadim Yanitskiy <axilirator@gmail.com> | |
| Mon, 17 Dec 2018 22:47:11 +0000 (18 05:47 +0700) | ||
| tree | f09ed1da637accf48bda434a899d2d73966a1d4e | treesnapshot (tar.gz zip) |
| parent | 8b3d49bd34271e1ffc5bb6910020e1479cd58b5d | commitdiff |
trx_toolkit/data_msg.py: add optional legacy message coding flag
Some transceivers (e.g. OsmoTRX) have inherited a rudiment from
OpenBTS - two dummy bytes at the end of TRX2L1 messages. Despite
they are absolutely useless, some L1 implementations, such as
trxcon and OpenBTS, still do expect them when checking
the message length.
Let's add an optional (disabled by default) argument to gen_msg(),
that would enable adding those two dummy bytes.
Change-Id: I0cf1314c399411886420176704cadd6e6d84787f
Some transceivers (e.g. OsmoTRX) have inherited a rudiment from
OpenBTS - two dummy bytes at the end of TRX2L1 messages. Despite
they are absolutely useless, some L1 implementations, such as
trxcon and OpenBTS, still do expect them when checking
the message length.
Let's add an optional (disabled by default) argument to gen_msg(),
that would enable adding those two dummy bytes.
Change-Id: I0cf1314c399411886420176704cadd6e6d84787f
| src/target/trx_toolkit/data_msg.py | diffblobblamehistory |