scope of scheduler.c and trx_sched_*

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/.

Neels Hofmeyr nhofmeyr at sysmocom.de
Wed Jun 29 16:10:51 UTC 2016


I notice that apparently osmo-bts-trx is the only caller of the trx_sched_*
API, yet it is implemented in common/scheduler.c and compiled to
libl1sched.a. Is osmo-bts-trx really the only caller?

Also in osmo-bts-trx, the "trx" to me means SDR, like B200.
But any BTS has one or more TRXs. So why isn't it osmo-bts-sdr?
That's why I thought: maybe trx_sched_ is for all BTS models?

Thanks for any clarification / confirmation :)

~Neels

-- 
- Neels Hofmeyr <nhofmeyr 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
* Geschäftsführer / Managing Directors: Harald Welte
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20160629/a893daf0/attachment.bin>


More information about the OpenBSC mailing list