Change in osmo-pcu[master]: direct-phy: fix handle_ph_ra_ind(): handle PH-RA.ind on PRACH SAPI

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/gerrit-log@lists.osmocom.org/.

fixeria gerrit-no-reply at lists.osmocom.org
Mon Mar 30 10:20:16 UTC 2020


fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-pcu/+/17669 )

Change subject: direct-phy: fix handle_ph_ra_ind(): handle PH-RA.ind on PRACH SAPI
......................................................................


Patch Set 1:

> Patch Set 1:
> 
> The question is whether the RA bursts on PTTCH are reported with what specific SAPI value.  If they are also reported as PRACH SAPI, then one would have to look at the TDMA multiplex tables in ordre to know if it's a PDTCH or a PTCCH.  The question is how to test properly.... I guess we'd need to have some OsmocomBB hack that can transmit RA at user-specified FN + timeslot and then observe what happens on uplink.

I think it would be much easier to hack Encoding::write_packet_uplink_assignment(), or rather write_tai() to unconditionally assign some TAI (e.g. 0), and then test with a regular phone.


-- 
To view, visit https://gerrit.osmocom.org/c/osmo-pcu/+/17669
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-pcu
Gerrit-Branch: master
Gerrit-Change-Id: Ib0a6da37de7a1db4cad2b96293b31b9f32e7d9eb
Gerrit-Change-Number: 17669
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <axilirator at gmail.com>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <axilirator at gmail.com>
Gerrit-CC: laforge <laforge at osmocom.org>
Gerrit-Comment-Date: Mon, 30 Mar 2020 10:20:16 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20200330/3fdfa8af/attachment.htm>


More information about the gerrit-log mailing list