I use it in a laboratory with 1-2 clients. It's about backing up that job when I've already invested time. It seems that the master branch is impossible for this. I have it in a private fork.

Is it possible in its current form to have it in any branch?
Can it at least stay in the gerrit?

Basically the main problem is that I link with the libsdr.so library but I can't publish the source codes. I don't have them.
Could I solve this with an open source (GPL) reimplementation of that library?



pá 11. 9. 2020 v 19:07 odesílatel Mychaela Falconia <mychaela.falconia@gmail.com> napsal:
Let me see if I understand the PCIeSDR proprietary libsdr.so situation
correctly.  There is a hardware vendor (Amarisoft) who produces a
piece of hardware, but refuses to provide FLOSS support for it, and
instead provides an essential layer (required for the device to work)
only in the form of a proprietary binary library with no source - is
this understanding correct?

Does this vendor have competitors?  Are there other companies who make
SDR devices in PCIe form factor, but who provide all necessary support
pieces in full source form under an Osmocom-compatible license?  Maybe
LimeSDR PCIe?  If such alternative non-proprietary vendors exist, why
not vote with your dollars against proprietary blobs by giving your
business to better vendors rather than Amarisoft?

OTOH if you personally (Xaver) already invested into Amarisoft
hardware and don't want your work to go to waste because of license
worship, I encourage you to maintain your own fork of OsmoTRX outside
of osmocom.org and thus out of reach of their license police.  I will
never use it myself or even look at it because this kind of SDR is not
my area of interest, but I am encouraging you as a matter of general
principle, just like my predecessor Che Guevara would have.

M~