This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-net-gprs@lists.osmocom.org/.
Harald Welte laforge at gnumonks.orgHi Bhargava,
On Tue, Mar 22, 2016 at 02:53:19PM +0000, Bhargava Abhyankar wrote:
> We have planned to support 11 bit RACH in osmo-pcu and osmo-bts. In
> this regard, we have a query related to layer 1 to osmo-bts
> interface, as described below.
given that the current format relates to the history of the omso-bts
project and the first PHY that we interfaced it with, I think if we make
some changes now to the L1 interface (including L1SAP), we could
actually clean things up.
To do so, I would suggest to
a) on L1SAP, extend ph_rach_ind_param with
* a uint16_t for 'ra'
* add a member 'is_11bit' to indicate 8/11 bit
* an enum to indicate the different burst types
(and change the osmo-bts-* implementations as well as common code to use
that updated definition)
b) on the PCU socket, perform similar changes to gsm_pcu_if_rach_ind
After performing above-mentioned changes, the formatting of the data
should be self-explanatory.
Regards,
Harald
--
- Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)