June 2016 - osmocom-sdr - lists.osmocom.org

Moving from trac to a single redmine
by Holger Freyther 25 Sep '16

25 Sep '16

Hi guys, I think some of us would like to move to redmine and start using public tickets more frequently. So in case we move there are some topics to be discussed and I would like to start with a couple of them right now. Tickets: Redmine has a global linear sequence of ticket numbers. If we move from many tracs to a single redmine we can either: * not import tickets * only import from one project * deal with changing ticket numbers In terms of installations the GMR trac is broken in regard to tickets, there are some for SDR that are probably not being fixed anytime soon, baseband might be relevant and OpenBSC is unlikely to be relevant. I don't think we have ever used ticket reference in OpenBSC commit messages so in terms of OpenBSC having changing ticket numbers would not be a big deal. E.g. we could add a custom field with the old trac number? Wiki: We have external references that should be redirected to the new place. Is there any way besides maintaining a list in the apache2/nginx configuration and making redirects as we find broken references? Can we proactively manage this? Is anybody willing to come up with a script and nginx configuration for doing this? kind regards holger

7 14

post a new release
by Joseph Poirier 22 Jul '16

22 Jul '16

If would be nice to have a newer official release available; installation using the package manager on many Linux distros gets a two year old librtlsdr that's missing the rtlsdr_set_tuner_bandwidth function (added about nine months ago), as well as, other nice updates and fixes. cheers, joe

6 12

Fwd: Patch for osmocom-sdr
by Mike Davis 24 Jun '16

24 Jun '16

Hi I can't sensibly use git-send-email as it wants to do the actual emailing on my behalf, and I use Gmail for this account. I tried sending via git-send-email directly to the list MX and SORBS blocked me, so I've attached the three patches as formatted by 'git format-patch' here. Regards Mike On Fri, Jun 24, 2016 at 9:46 AM, Sylvain Munaut <246tnt(a)gmail.com> wrote: > Hi, > > > Initially I tried to do a Pull Request on the Github repository, > > Yeah we don't use github. > > tbh I'm not even sure who's doing the mirror there ... > > > but was > > told I should send a patch to this mailing list. What format should I > use to > > send the patch? > > See the doc for git-send-email > > You create a git commit with your patch then use that to send it by > mail to the list and it will handle the formatting for you and making > sure the patch isn't mangled by your mail client. > > Cheers, > > Sylvain >

1 0

Patch for osmocom-sdr
by Mike Davis 24 Jun '16

24 Jun '16

Hi I have a patch for the gr-osmosdr project that I am hoping you will be able to merge into the repo. The patch makes it possible to choose which hackrf is opened by the sink component. It also moves the hackrf_open code into a separate, shared source file that is used by both the sink and the source components. Initially I tried to do a Pull Request on the Github repository, but was told I should send a patch to this mailing list. What format should I use to send the patch? Regards Mike

2 1

merge request - update to soapy_support
by Josh Blum 24 Jun '16

24 Jun '16

Hey list, I've pushed some minor fixes to the soapy_support branch. With these fixes I was able to use the siggen gui app with the LimeSDR. More details in the commits. http://git.osmocom.org/gr-osmosdr/log/?h=soapy_support I would appreciate if this can be merged into master. Thanks! -josh

1 0

Patch for gr-osmosdr
by Mike Davis 23 Jun '16

23 Jun '16

Hi I have a patch for the gr-osmosdr project that I am hoping you will be able to merge into the repo. The patch makes it possible to choose which hackrf is opened by the sink component. It also moves the hackrf_open code into a separate, shared source file that is used by both the sink and the source components. Initially I tried to do a Pull Request on the Github repository, but was told I should send a patch to this mailing list. What format should I use to send the patch? Regards Mike Davis

1 0

Re: [PATCH] librtlsdr.pc: use "Require: libusb-1.0" instead of "Libs: -lusb-1.0"
by Bjørn Forsman 07 Jun '16

07 Jun '16

On 31 October 2014 at 08:54, Bjørn Forsman <bjorn.forsman(a)gmail.com> wrote: > Using "Libs: -lusb-1.0" assumes the linker knows where libusb is > located. Using "Require: libusb-1.0" is more correct as it uses > pkg-config to locate the required package and provides correct flags > (both -l and -L). > > This fix is needed to build programs that depend on librtlsdr on > NixOS[1]. (Because there is no "default" linker serach path on NixOS.) > > [1]: http://nixos.org/ > --- > librtlsdr.pc.in | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/librtlsdr.pc.in b/librtlsdr.pc.in > index 5e55049..76b4190 100644 > --- a/librtlsdr.pc.in > +++ b/librtlsdr.pc.in > @@ -7,5 +7,6 @@ Name: RTL-SDR Library > Description: C Utility Library > Version: @VERSION@ > Cflags: -I${includedir}/ @RTLSDR_PC_CFLAGS@ > -Libs: -L${libdir} -lrtlsdr -lusb-1.0 > +Libs: -L${libdir} -lrtlsdr > Libs.private: @RTLSDR_PC_LIBS@ > +Requires: libusb-1.0 > -- Ping. (Oh, and please fixup my commit message typo (s/serach/search/) if/when you apply it.) Best regards, Bjørn Forsman

1 0

librtlsdr API documentation
by Neoklis Kyriazis 02 Jun '16

02 Jun '16

Hi I have purchased an RTL2832/R820Tsdr unit from NooElec and I would like to start writing code for an application to decode weather images from satellite APT transmissions on 137 MHz. I already have written an application to decode such images, received by an old analogue FM receiver, but I feel it can be used with the RTL/SDR dongle as well. To do this I need some documentation on the librtlsdr API but I have not found any with my searches. Is there any documentation for librtlsdr API or any other documentation on how to use available funtions in the lib? My thanks in advance. -- Best Regards Neoklis - Ham Radio Call:5B4AZ http://www.5b4az.org/

2 2