OsmocomBB MS-side GSM Protocol stack (L1, L2, L3) including firmware https://osmocom.org/projects/baseband
Go to file
Andreas Eversberg 34e3d809e1 mobile: Fix PCS ARFCN handling: PCS can only be ARFCN 512..810
While it is correct to use the band indicator from SI1 rest octets,
it may only be applied for ARFCN values in the range 512..810.

The function gsm_refer_pcs() is used to determine, if the cell (which
'talks' about ARFCNs) refers to them PCS or DCS channels. It returns
true, if it refers to PCS, but this only means that ARFCNs in the range
512..810 are PCS channels, not all ARFCNs.

The new function gsm_arfcn_refer_pcs() is used to add the PCS flag to an
ARFCN, if the given cell refers to PCS and the given ARFCN is in the PCS
range 512..810.

Change-Id: Id99c8534bf853f4f24f99364790c1ac1df6cc007
Related: OS#6078
2023-11-24 17:49:30 +01:00
contrib contrib/jenkins.sh: uncomment verify_value_string_arrays_are_terminated.py 2023-05-17 10:55:55 +00:00
doc doc/examples/modem: Update modem.cfg with new features 2023-04-26 14:14:29 +02:00
include ASCI: Add UIC support to random access burst 2023-09-28 10:42:38 +02:00
src mobile: Fix PCS ARFCN handling: PCS can only be ARFCN 512..810 2023-11-24 17:49:30 +01:00
.gitignore doc/manuals: integrate into this repository 2018-12-04 12:14:59 +00:00
.gitreview Add 'git review' config file 2017-09-07 12:21:24 +02:00