Unfix BUG in GSM322.c and prim_pm.c

Sylvain Munaut 246tnt at gmail.com
Mon May 21 13:22:01 UTC 2012


> 1. PCS arfcn range calculation seems to be incorrect. The initial arfcn and
> final
> are passed with extremely high range values in reverse order.

Are you sure the "high range" is not just caused by the ARFCN_PCS flags ?
(which is 16384 IIRC)

Since DCS and PCS arfcn # overlap, PCS is treated specially and
remapped with 16384 added to them.

Cheers,

    Sylvain




More information about the baseband-devel mailing list