From 0f227d802b1ed22c8863a794675222ceaac2fd8c Mon Sep 17 00:00:00 2001 From: Vadim Yanitskiy Date: Wed, 12 Jul 2017 17:40:22 +0700 Subject: [PATCH] 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 --- src/host/trxcon/trx_if.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/host/trxcon/trx_if.c b/src/host/trxcon/trx_if.c index eb868ce92..1ee9440ed 100644 --- a/src/host/trxcon/trx_if.c +++ b/src/host/trxcon/trx_if.c @@ -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;