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/OpenBSC@lists.osmocom.org/.
Xaver Zu xaver1zu at gmail.comHi, I updated API and rebased it. It works more stable with new version of osmo-bts. What exactly does a "device backend" mean? Is it content of osmo-trx/Transceiver52M/device/pciesdr/ or lower layers (libsdr, kernel drivers or HW)? This crash happen after device stop - start (caused by cmd PWROFF from osmo-bts). PCIESDRDevice.cpp:363 [tid=140137302865664] rc < 0 <0002> PCIESDRDevice.cpp:364 [tid=140137302865664] Sample buffer: Requested I haven't found a working solution yet. Starting the demon again helps. I managed to reach an uptime of more than 3 hours with one MS connected. So I decide push it into gerrit for review https://gerrit.osmocom.org/c/osmo-trx/+/19548 Are you considering adding support for floating format samples to the radio interface? The proprietary libsdr.so library (driver from manufacturer) expects samples in float format. I have to convert short to float again during Rx / Tx. I received a feedbak from laforge with a request to complete the PCIeSDR description. Is it possible to create a page on the wiki for this purpose? Regards XK1Zu so 18. 7. 2020 v 18:19 odesílatel Pau Espin Pedrol <pespin at sysmocom.de> napsal: > Hi, > > without looking into much detail at your branch, I should suggest: > > * Rebase your work on top of current osmo-trx master, the base commit > you use is uite old and the API has changed a bit since then, with some > fixes and improvements. > > * Make sure you run both osmo-trx and osmo-bts-trx with RR scheduler > (realtime). For instance, osmo-trx VTY cmd "rt-prio 18", and > osmo-bts-trx cmd line arg "-r 1". > > * From what i see in the logs, it looks like you have some issues with > how you are managing the tmestamps inside your device backend, so > something is not being done correctly in there most probably, then 0 is > returned and osmo-trx upper layers decide to stop the process. > > Once you have something working acceptably fine (MS can use the network > more or less reliably, and osmo-trx doesn't stop or crash), I'm happy to > review your patch in gerrit. > > Regards, > Pau > > -- > - Pau Espin Pedrol <pespin at sysmocom.de> http://www.sysmocom.de/ > ======================================================================= > * sysmocom - systems for mobile communications GmbH > * Alt-Moabit 93 > * 10559 Berlin, Germany > * Sitz / Registered office: Berlin, HRB 134158 B > * Geschaeftsfuehrer / Managing Director: Harald Welte > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20200808/13a66eda/attachment.htm>