From b570cd532aaa925c7a3815777be8ea5dc6ddfa51 Mon Sep 17 00:00:00 2001 From: Harald Welte Date: Sat, 11 Aug 2018 13:49:41 +0200 Subject: trxcon: distinguish between unimplemented and unknown messages Let's differentiate between 'expected' unimplemented messages like L1CTL_NEIGH_PM_REQ and truly unknonw message types. Change-Id: Id76993056fb514e6fb0242d505205316c61bb965 --- src/host/trxcon/l1ctl.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/host/trxcon/l1ctl.c b/src/host/trxcon/l1ctl.c index b0a4c6dd..230ef0a9 100644 --- a/src/host/trxcon/l1ctl.c +++ b/src/host/trxcon/l1ctl.c @@ -792,6 +792,16 @@ int l1ctl_rx_cb(struct l1ctl_link *l1l, struct msgb *msg) return l1ctl_rx_tch_mode_req(l1l, msg); case L1CTL_CRYPTO_REQ: return l1ctl_rx_crypto_req(l1l, msg); + + /* Not (yet) handled messages */ + case L1CTL_NEIGH_PM_REQ: + case L1CTL_DATA_TBF_REQ: + case L1CTL_TBF_CFG_REQ: + case L1CTL_DM_FREQ_REQ: + case L1CTL_SIM_REQ: + LOGP(DL1C, LOGL_NOTICE, "Ignoring unsupported message " + "(type=%u)\n", l1h->msg_type); + return -ENOTSUP; default: LOGP(DL1C, LOGL_ERROR, "Unknown MSG type %u: %s\n", l1h->msg_type, osmo_hexdump(msgb_data(msg), msgb_length(msg))); -- cgit v1.2.3