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/.
Jacob Erlbeck jacob01 at gmx.netHi, what exactly is your definition of 'rach_type'? Could you please either add a reference to the document where this notion is specified, or if there is none, a specification of its value range. Is the used TSC (TS1 or TS2 in case of EGPRS) is mapped to this value? If not, this should IMHO also be added to have all relevant RACH information included, since this is closely related to the 11 bit RACH type which cannot be fully used for EGPRS without that information. See 44.060, 11.2.5a for details. Jacob On 21.03.2016 16:03, Bhargava Abhyankar wrote: > Interface changes in osmo-pcu towards osmo-bts to > receive 11 bit RACH. > The interface version number is increased by 1. > - int rcv_rach(uint8_t ra, uint32_t Fn, int16_t qta); > + int rcv_rach(uint16_t ra, uint32_t Fn, int16_t qta, > + uint8_t rach_type = 0); > struct gsm_pcu_if_rach_ind { > uint8_t sapi; > - uint8_t ra; > + uint16_t ra; > int16_t qta; > uint32_t fn; > uint16_t arfcn; > + uint8_t rach_type; > } __attribute__ ((packed));