diff options
| author | Harald Welte <laforge@gnumonks.org> | 2017-12-03 10:54:02 +0100 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2017-12-03 10:01:54 +0000 |
| commit | a7bfb6c8dabcba6fb3534c4733d88fb9e466ae15 (patch) | |
| tree | 8af680310b2112ebdf2d3428d73a3b21f7140e75 /src/osmo-bts-octphy/l1_if.c | |
| parent | 57ce53d8aac6dbd4ac10585b7b812c6021a19095 (diff) | |
osmo-bts-octphy: Remove bogus warning about BS_AG_BLKS_RES
Contrary to osmo-bts-sysmo, the OCTPHY-2G does not have different L1
SAPI for AGCH and PCH. It uses cOCTVC1_GSM_SAPI_ENUM_PCH_AGCH for both,
and we convert that to the cbits=0x12 (Downlink CCCH) on the L1SAP.
The code above L1SAP can hence freely decide if it wants to respond with
an AGCH or PCH message, based on its knowledge of BS_AG_BLKS_RES,
without the OCTPHY specific code having to do anything about it.
Hence, there's nothing to do, and the warning can be removed
Change-Id: Ic1038b8dc57bdaf05493cd8479355b960275ea41
Related: OS#1575
Diffstat (limited to 'src/osmo-bts-octphy/l1_if.c')
| -rw-r--r-- | src/osmo-bts-octphy/l1_if.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/osmo-bts-octphy/l1_if.c b/src/osmo-bts-octphy/l1_if.c index e4ab5385..fce34841 100644 --- a/src/osmo-bts-octphy/l1_if.c +++ b/src/osmo-bts-octphy/l1_if.c @@ -516,7 +516,6 @@ static int ph_data_req(struct gsm_bts_trx *trx, struct msgb *msg, } else if (L1SAP_IS_CHAN_BCCH(chan_nr)) { sapi = cOCTVC1_GSM_SAPI_ENUM_BCCH; } else if (L1SAP_IS_CHAN_AGCH_PCH(chan_nr)) { -#warning Set BS_AG_BLKS_RES sapi = cOCTVC1_GSM_SAPI_ENUM_PCH_AGCH; } else { LOGP(DL1C, LOGL_NOTICE, "unknown prim %d op %d " |