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/.
Harald Welte laforge at gnumonks.orgHi Max,
On Wed, Mar 23, 2016 at 03:44:08PM +0100, Max wrote:
> Shouldn't we move the code in question to src/common than?
No, the code is similar but not identical, and the L1 interfaces of the
underlying PHY are not guaranteed to stay as similar as they are.
So some of the general structure can probably be further common-ized,
but the details regarding the L1 interface primitives will still stay
PHY (bts-model-)specific.
Also, the point is that so far nobody has volunteered to do (or fund)
such an effort.
It is typically relatively easy for companies to take care / ownership /
funding of the driver for their specific hardware, rather it is for
refactoring and general code improvement. This is not specific to
OsmoBTS, but you can also see this quite a lot if you look at Linux
kernel development until fairly recently.
It takes both an interest in long-term effects as well as a deep
understanding about the nature of collaborative free software
development processes to invest in the improvement of the (core/common)
code.
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)