phone-side
/
osmocom-bb
mirror of https://gerrit.osmocom.org/osmocom-bb
9
0
Fork 0
Code Issues Releases Wiki Activity

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
This commit is contained in:
Vadim Yanitskiy 2017-07-12 17:40:22 +07:00
parent a692cacdfc
commit 0f227d802b
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/host/trxcon/trx_if.c
View File

@ -516,6 +516,7 @@ rsp_error:
/* 1 byte RSSI in -dBm */
/* 2 bytes correlator timing offset in 1/256 symbol steps, 2's-comp, BE */
/* 148 bytes soft symbol estimates, 0 -> definite "0", 255 -> definite "1" */
/* 2 bytes are not used, but being sent by OsmoTRX */
/* */
/* Transmit Data Burst: */
/* 1 byte timeslot index */
@ -538,7 +539,7 @@ static int trx_data_read_cb(struct osmo_fd *ofd, unsigned int what)
if (len <= 0)
return len;
if (len != 156) {
if (len != 158) {
LOGP(DTRX, LOGL_ERROR, "Got data message with invalid length "
"'%d'\n", len);
return -EINVAL;