From nkcyham at yahoo.com Wed Jun 1 04:23:39 2016 From: nkcyham at yahoo.com (Neoklis Kyriazis) Date: Wed, 1 Jun 2016 04:23:39 +0000 (UTC) Subject: librtlsdr API documentation References: <2103355871.2720573.1464755019201.JavaMail.yahoo.ref@mail.yahoo.com> Message-ID: <2103355871.2720573.1464755019201.JavaMail.yahoo@mail.yahoo.com> 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/ From lucas at teske.com.br Wed Jun 1 16:55:45 2016 From: lucas at teske.com.br (Lucas Teske) Date: Wed, 1 Jun 2016 13:55:45 -0300 Subject: librtlsdr API documentation In-Reply-To: <2103355871.2720573.1464755019201.JavaMail.yahoo@mail.yahoo.com> References: <2103355871.2720573.1464755019201.JavaMail.yahoo.ref@mail.yahoo.com> <2103355871.2720573.1464755019201.JavaMail.yahoo@mail.yahoo.com> Message-ID: <574F1391.6040409@teske.com.br> Hi Neoklis, If you check the librtlsdr headers the functions have a comment section explaining what they do. Also the source code of librtlsdr is pretty straight-forward to understand. Lucas Em 01/06/2016 01:23, Neoklis Kyriazis escreveu: > 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/ From nkcyham at yahoo.com Thu Jun 2 03:19:58 2016 From: nkcyham at yahoo.com (Neoklis Kyriazis) Date: Thu, 2 Jun 2016 03:19:58 +0000 (UTC) Subject: librtlsdr API documentation In-Reply-To: <574F1391.6040409@teske.com.br> References: <2103355871.2720573.1464755019201.JavaMail.yahoo.ref@mail.yahoo.com> <2103355871.2720573.1464755019201.JavaMail.yahoo@mail.yahoo.com> <574F1391.6040409@teske.com.br> Message-ID: <10969143.3406357.1464837598479.JavaMail.yahoo@mail.yahoo.com> OK Lucas Thanks for the info, I will check it out. -- Best Regards Neoklis - Ham Radio Call:5B4AZ http://www.5b4az.org/ From bjorn.forsman at gmail.com Tue Jun 7 11:04:56 2016 From: bjorn.forsman at gmail.com (=?UTF-8?Q?Bj=C3=B8rn_Forsman?=) Date: Tue, 7 Jun 2016 13:04:56 +0200 Subject: [PATCH] librtlsdr.pc: use "Require: libusb-1.0" instead of "Libs: -lusb-1.0" In-Reply-To: <1414742045-24064-1-git-send-email-bjorn.forsman@gmail.com> References: <1414742045-24064-1-git-send-email-bjorn.forsman@gmail.com> Message-ID: On 31 October 2014 at 08:54, Bj?rn Forsman 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 From josh at joshknows.com Fri Jun 24 06:04:22 2016 From: josh at joshknows.com (Josh Blum) Date: Thu, 23 Jun 2016 23:04:22 -0700 Subject: merge request - update to soapy_support Message-ID: <576CCD66.5000004@joshknows.com> 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 From dodgymike at gmail.com Fri Jun 24 07:40:27 2016 From: dodgymike at gmail.com (Mike Davis) Date: Fri, 24 Jun 2016 09:40:27 +0200 Subject: Patch for osmocom-sdr Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Fri Jun 24 07:46:51 2016 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 24 Jun 2016 09:46:51 +0200 Subject: Patch for osmocom-sdr In-Reply-To: References: Message-ID: 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 From dodgymike at gmail.com Fri Jun 24 13:30:23 2016 From: dodgymike at gmail.com (Mike Davis) Date: Fri, 24 Jun 2016 15:30:23 +0200 Subject: Fwd: Patch for osmocom-sdr In-Reply-To: References: Message-ID: 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 at 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fixed-README-grammar.patch Type: text/x-patch Size: 569 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-Moved-hackrf-device-open-logic-to-common-function-fo.patch Type: text/x-patch Size: 8219 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0003-README-grammar-fix.patch Type: text/x-patch Size: 828 bytes Desc: not available URL: From dodgymike at gmail.com Thu Jun 23 14:03:52 2016 From: dodgymike at gmail.com (Mike Davis) Date: Thu, 23 Jun 2016 16:03:52 +0200 Subject: Patch for gr-osmosdr Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: