From mike at flomp.net Wed Aug 5 20:19:43 2020 From: mike at flomp.net (Mike Walters) Date: Wed, 5 Aug 2020 21:19:43 +0100 Subject: [PATCH] gr-osmosdr: fix hackrf_source signedness Message-ID: The LUT changes in 2e7d343fed inadvertently started interpreting samples as unsigned. This change puts it back to signed (and fixes an outdated comment). -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-HackRF-fix-hackrf_source-signedness.patch Type: text/x-patch Size: 1569 bytes Desc: not available URL: From troy at troycurtisjr.com Tue Aug 11 02:12:41 2020 From: troy at troycurtisjr.com (Troy Curtis Jr) Date: Mon, 10 Aug 2020 22:12:41 -0400 Subject: GNU Radio 3.9 support for gr-osmosdr Message-ID: Howdy guys. I see some work around getting gr-osmosdr working nicely with GR 3.8, but have there been any discussions around GR 3.9 (really current 'master')? I recently decided to pick GNU Radio back up and hook up my rtl dongle. In particular, I wanted to dust off my C++ chops that I haven't been able to exercise in my current $DAYJOB. Naturally then I started with GNU Radio master! It looks like one major change is that they have replaced swig with pybind, which means that the current gr-osmosdr can't even begin to work. So has there been any discussion about the porting effort necessary to move it over? I'm interested in starting to poke at getting it working under current GR 3.9/master, but had a few questions before I started: 1) Has anyone else started on the changes that I could coordinate with? 2) Is there generally any attempt at tracking gr master, or do you typically only target release branches? 3) Am I putting the cart before the horse and really need to focus any of my willingness to help on getting the GR 3.8 solid (if it isn't already)? Thanks for time, Troy -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Tue Aug 11 06:52:17 2020 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 11 Aug 2020 08:52:17 +0200 Subject: GNU Radio 3.9 support for gr-osmosdr In-Reply-To: References: Message-ID: > 2) Is there generally any attempt at tracking gr master, or do you typically only target release branches? Historically, we only target release branch. "Master" only gets supported when the first "rc" comes out and the GR API is declared stable. Once the new stable release come it becomes the only supported one and what gr-osmosdr 'master' targets. The "old" release becomes a branch and pretty much frozen. Now Hoerchen who's taking over gr-osmosdr may decide to change that scheme ... up to him. Cheers, Sylvain From troy at troycurtisjr.com Tue Aug 11 11:32:27 2020 From: troy at troycurtisjr.com (Troy Curtis Jr) Date: Tue, 11 Aug 2020 07:32:27 -0400 Subject: GNU Radio 3.9 support for gr-osmosdr In-Reply-To: References: Message-ID: On Tue, Aug 11, 2020 at 2:52 AM Sylvain Munaut <246tnt at gmail.com> wrote: > > Historically, we only target release branch. > "Master" only gets supported when the first "rc" comes out and the GR > API is declared stable. > Yeah that makes perfect sense. Who knows what more changes happen on GR master branch before they cut a release? Once I thought about a bit I realized it would be trying to constantly hit a moving target. > > Now Hoerchen who's taking over gr-osmosdr may decide to change that > scheme ... up to him. Ah excellent, that answers another question I had and didn't ask, whether anyone had taken up the project lead mantle. Good to hear. I'm sure that the current process is the most reasonable one. If I really want to give it a go, I can always just have a separate branch with no expectation of hitting master until after GR 3.9 hits. Thanks for the response! Troy From 0xloem at gmail.com Tue Aug 25 02:34:29 2020 From: 0xloem at gmail.com (Karl Semich) Date: Mon, 24 Aug 2020 22:34:29 -0400 Subject: gr-osmosdr maintenance situation In-Reply-To: References: Message-ID: Hi Sylvain, list. On Tue, Aug 11, 2020 at 2:52 AM Sylvain Munaut <246tnt at gmail.com> wrote: ... snip ... > Now Hoerchen who's taking over gr-osmosdr may decide to change that > scheme ... up to him. Could anyone give any update on the gr-osmosdr situation? I don't track the project closely, but a quick search doesn't turn up any posts from a Hoerchen to this list. Given the number of pending patches to gr-osmosdr, would it be helpful to have more than just one maintainer on the project? Are there any plans yet for merging patches, or a capacity-level with regard to how many it is helpful to bring on board at first, or what could be done to them to ease consideration? Thanks so much, Karl Semich From 246tnt at gmail.com Tue Aug 25 16:10:37 2020 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 25 Aug 2020 18:10:37 +0200 Subject: gr-osmosdr maintenance situation In-Reply-To: References: Message-ID: Hi, > Given the number of pending patches to gr-osmosdr, would it be helpful > to have more than just one maintainer on the project? What pending patches ? All the ones that have been sent here (and are actually mergeable) have been merged beginning of the month by Hoerchen according to the git logs. Cheers, Sylvain From 246tnt at gmail.com Tue Aug 25 17:58:58 2020 From: 246tnt at gmail.com (Sylvain Munaut) Date: Tue, 25 Aug 2020 19:58:58 +0200 Subject: gr-osmosdr maintenance situation In-Reply-To: References: Message-ID: We don't go looking forks ... if something is not posted to this ML, we won't see it. Anything posted or submitted from before the 3.8 port, was also discarded, when I did the adaptation I didn't go and look in the archive to see if there was anything still relevant ... If it was I figured the author would rebase the patch to apply cleanly onto the new branch and repost if he cared and if he didn't then it must not have been that important. Cheers, Sylvain From bclay1297 at gmail.com Wed Aug 12 19:24:15 2020 From: bclay1297 at gmail.com (Bruce Clay) Date: Wed, 12 Aug 2020 19:24:15 -0000 Subject: where to post rtl-sdr questions Message-ID: Where is the best place to post librtlsdr developer questions? Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From baffo32 at gmail.com Tue Aug 25 16:43:07 2020 From: baffo32 at gmail.com (Karl Semich) Date: Tue, 25 Aug 2020 16:43:07 -0000 Subject: gr-osmosdr maintenance situation In-Reply-To: References: Message-ID: I don't have access to the git not much web for now, but I am very surprised by what you say. Earlier an extensive list of forks was posted here, all with unmerged fixes to address, with no reply to the post. Over the past couple years, there was one month when I was the only person posting to this list, and all my posts were patches that still have received no reply. Thanks for pointing me towards the git history to find Hoerchen. On Tue, Aug 25, 2020, 12:10 PM Sylvain Munaut <246tnt at gmail.com> wrote: > Hi, > > > Given the number of pending patches to gr-osmosdr, would it be helpful > > to have more than just one maintainer on the project? > > What pending patches ? > All the ones that have been sent here (and are actually mergeable) > have been merged beginning of the month by Hoerchen according to the > git logs. > > > Cheers, > > Sylvain > On Aug 25, 2020 12:10 PM, "Sylvain Munaut" <246tnt at gmail.com> wrote: Hi, > Given the number of pending patches to gr-osmosdr, would it be helpful > to have more than just one maintainer on the project? What pending patches ? All the ones that have been sent here (and are actually mergeable) have been merged beginning of the month by Hoerchen according to the git logs. Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: