From brian at brianmwaters.net Tue Nov 5 22:05:47 2019 From: brian at brianmwaters.net (Brian Waters) Date: Tue, 05 Nov 2019 17:05:47 -0500 Subject: Small patch to fix building librtlsdr on OpenBSD Message-ID: Gets rid of librt, which doesn't exist on OpenBSD. The version of librtlsdr in the OpenBSD ports tree is extremely old (~2013), so this should help some users. Tested against tag 0.6.0, but it should apply just fine to HEAD. Thanks, Brian Waters -- Brian M. Waters brian at brianmwaters.net -------------- next part -------------- A non-text attachment was scrubbed... Name: openbsd.patch Type: text/x-patch Size: 411 bytes Desc: not available URL: From brian at brianmwaters.net Fri Nov 8 22:49:39 2019 From: brian at brianmwaters.net (Brian Waters) Date: Fri, 08 Nov 2019 17:49:39 -0500 Subject: Small patch to fix building librtlsdr on OpenBSD In-Reply-To: References: Message-ID: <35965440-b6fd-4a49-8534-6b9feba4d556@www.fastmail.com> Looks like I mistakenly included the patch as an attachment, so it may not have gone through. Here it is: diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt index 07d64ab..015fd48 100644 --- a/src/CMakeLists.txt +++ b/src/CMakeLists.txt @@ -125,7 +125,7 @@ if(UNIX) target_link_libraries(rtl_fm m) target_link_libraries(rtl_adsb m) target_link_libraries(rtl_power m) -if(APPLE) +if(APPLE OR CMAKE_SYSTEM MATCHES "OpenBSD") target_link_libraries(rtl_test m) else() target_link_libraries(rtl_test m rt) Thanks, BW -- Brian M. Waters brian at brianmwaters.net On Tue, Nov 5, 2019, at 5:05 PM, Brian Waters wrote: > Gets rid of librt, which doesn't exist on OpenBSD. The version of > librtlsdr in the OpenBSD ports tree is extremely old (~2013), so this > should help some users. > > Tested against tag 0.6.0, but it should apply just fine to HEAD. > > Thanks, > Brian Waters > > -- > Brian M. Waters > brian at brianmwaters.net > Attachments: > * openbsd.patch From adrian at freebsd.org Sat Nov 9 16:56:27 2019 From: adrian at freebsd.org (Adrian Chadd) Date: Sat, 9 Nov 2019 08:56:27 -0800 Subject: Small patch to fix building librtlsdr on OpenBSD In-Reply-To: <35965440-b6fd-4a49-8534-6b9feba4d556@www.fastmail.com> References: <35965440-b6fd-4a49-8534-6b9feba4d556@www.fastmail.com> Message-ID: is this applicable to the other BSDs too? Ideally the rule would be "only link in rt if it's present", right? -adrian On Sat, 9 Nov 2019 at 03:08, Brian Waters wrote: > > Looks like I mistakenly included the patch as an attachment, so it may not have gone through. Here it is: > > diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt > index 07d64ab..015fd48 100644 > --- a/src/CMakeLists.txt > +++ b/src/CMakeLists.txt > @@ -125,7 +125,7 @@ if(UNIX) > target_link_libraries(rtl_fm m) > target_link_libraries(rtl_adsb m) > target_link_libraries(rtl_power m) > -if(APPLE) > +if(APPLE OR CMAKE_SYSTEM MATCHES "OpenBSD") > target_link_libraries(rtl_test m) > else() > target_link_libraries(rtl_test m rt) > > Thanks, > BW > > -- > Brian M. Waters > brian at brianmwaters.net > > On Tue, Nov 5, 2019, at 5:05 PM, Brian Waters wrote: > > Gets rid of librt, which doesn't exist on OpenBSD. The version of > > librtlsdr in the OpenBSD ports tree is extremely old (~2013), so this > > should help some users. > > > > Tested against tag 0.6.0, but it should apply just fine to HEAD. > > > > Thanks, > > Brian Waters > > > > -- > > Brian M. Waters > > brian at brianmwaters.net > > Attachments: > > * openbsd.patch From brian at brianmwaters.net Sat Nov 9 17:18:00 2019 From: brian at brianmwaters.net (Brian Waters) Date: Sat, 09 Nov 2019 12:18:00 -0500 Subject: Small patch to fix building librtlsdr on OpenBSD Message-ID: <20191109171802.9E9F180059@mailuser.nyi.internal> Based on some cursory googling, it's _not_ needed for FreeBSD, but I haven't tested. I'm not sure about the others. A check for librt.so would be good; something like autoconf's AC_SEARCH_LIBS that actually searches libs for clock_get time() would be best. I don't know what CMake has to offer in that regard. BWOn Nov 9, 2019 11:56 AM, Adrian Chadd wrote: > > is this applicable to the other BSDs too? > > Ideally the rule would be "only link in rt if it's present", right? > > > -adrian > > On Sat, 9 Nov 2019 at 03:08, Brian Waters wrote: > > > > Looks like I mistakenly included the patch as an attachment, so it may not have gone through. Here it is: > > > > diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt > > index 07d64ab..015fd48 100644 > > --- a/src/CMakeLists.txt > > +++ b/src/CMakeLists.txt > > @@ -125,7 +125,7 @@ if(UNIX) > >? target_link_libraries(rtl_fm m) > >? target_link_libraries(rtl_adsb m) > >? target_link_libraries(rtl_power m) > > -if(APPLE) > > +if(APPLE OR CMAKE_SYSTEM MATCHES "OpenBSD") > >????? target_link_libraries(rtl_test m) > >? else() > >????? target_link_libraries(rtl_test m rt) > > > > Thanks, > > BW > > > > -- > > Brian M. Waters > > brian at brianmwaters.net > > > > On Tue, Nov 5, 2019, at 5:05 PM, Brian Waters wrote: > > > Gets rid of librt, which doesn't exist on OpenBSD. The version of > > > librtlsdr in the OpenBSD ports tree is extremely old (~2013), so this > > > should help some users. > > > > > > Tested against tag 0.6.0, but it should apply just fine to HEAD. > > > > > > Thanks, > > > Brian Waters > > > > > > -- > > > Brian M. Waters > > > brian at brianmwaters.net > > > Attachments: > > > * openbsd.patch From brian at brianmwaters.net Mon Nov 11 06:16:11 2019 From: brian at brianmwaters.net (Brian Waters) Date: Mon, 11 Nov 2019 01:16:11 -0500 Subject: [PATCH] build gr-iqbal w/ clang Message-ID: <0a4991d2-8051-4e8b-8f02-55b97a92f6e2@www.fastmail.com> Clang doesn't automatically define the "complex" keyword like old versions of GCC apparently used to. Appending this little check enabled compiling gr-iqbal w/ Clang, which is now the default compiler on OpenBSD and I think FreeBSD too. diff --git a/lib/optimize_c.cc b/lib/optimize_c.cc index 2cad998..6c8b706 100644 --- a/lib/optimize_c.cc +++ b/lib/optimize_c.cc @@ -31,7 +31,7 @@ __GNUC_PATCHLEVEL__ \ ) -#if GCC_VERSION >= 40800 +#if GCC_VERSION >= 40800 || defined(__clang__) # define complex _Complex # undef _GLIBCXX_HAVE_COMPLEX_H #endif -- Brian M. Waters brian at brianmwaters.net From axilirator at gmail.com Tue Nov 12 12:46:35 2019 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Tue, 12 Nov 2019 19:46:35 +0700 Subject: [PATCH] apps/osmocom_fft: fix compatibility with Python 3: print needs parentheses Message-ID: <20191112124635.679831-1-axilirator@gmail.com> --- apps/osmocom_fft | 42 +++++++++++++++++++++--------------------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/apps/osmocom_fft b/apps/osmocom_fft index da38861..0110d19 100755 --- a/apps/osmocom_fft +++ b/apps/osmocom_fft @@ -117,7 +117,7 @@ class app_top_block(stdgui2.std_top_block, pubsub): try: self.src.get_sample_rates().start() except RuntimeError: - print "Source has no sample rates (wrong device arguments?)." + print("Source has no sample rates (wrong device arguments?).") sys.exit(1) # Set the antenna @@ -150,18 +150,18 @@ class app_top_block(stdgui2.std_top_block, pubsub): gain_names = self.src.get_gain_names() for name in gain_names: range = self.src.get_gain_range(name) - print "%s gain range: start %d stop %d step %d" % (name, range.start(), range.stop(), range.step()) + print("%s gain range: start %d stop %d step %d" % (name, range.start(), range.stop(), range.step())) if options.gains: for tuple in options.gains.split(","): name, gain = tuple.split(":") gain = int(gain) - print "Setting gain %s to %d." % (name, gain) + print("Setting gain %s to %d." % (name, gain)) self.src.set_gain(gain, name) if self._verbose: rates = self.src.get_sample_rates() - print 'Supported sample rates %d-%d step %d.' % (rates.start(), rates.stop(), rates.step()) + print('Supported sample rates %d-%d step %d.' % (rates.start(), rates.stop(), rates.step())) if options.center_freq is None: freq = self.src.get_center_freq() @@ -221,7 +221,7 @@ class app_top_block(stdgui2.std_top_block, pubsub): #force update on pubsub keys #for key in (SAMP_RATE_KEY, BWIDTH_KEY, CENTER_FREQ_KEY, FREQ_CORR_KEY): - #print key, "=", self[key] + #print(key, "=", self[key]) #self[key] = self[key] if options.fosphor: @@ -422,7 +422,7 @@ class app_top_block(stdgui2.std_top_block, pubsub): try: bw_range = self[BWIDTH_RANGE_KEY] - #print bw_range.to_pp_string() + #print(bw_range.to_pp_string()) if bw_range.start() < bw_range.stop(): bwidth_vbox = forms.static_box_sizer(parent=self.panel, label="Bandwidth", @@ -537,14 +537,14 @@ class app_top_block(stdgui2.std_top_block, pubsub): self.rec_file_name = self.record_to_filename() - print "Recording samples to ", self.rec_file_name + print("Recording samples to ", self.rec_file_name) self.file_sink.open(self.rec_file_name); else: self.sample_rate_text.Enable() self.record_text.Enable() self.file_sink.close() - print "Finished recording to", self.rec_file_name + print("Finished recording to", self.rec_file_name) forms.toggle_button( sizer=rec_hbox, @@ -732,9 +732,9 @@ class app_top_block(stdgui2.std_top_block, pubsub): self.src.set_dc_offset( correction ) if self._verbose: - print "Set DC offset to", correction + print("Set DC offset to", correction) except RuntimeError as ex: - print ex + print(ex) def set_iq_balance_mode(self, iq_balance_mode): if iq_balance_mode == 1: @@ -761,16 +761,16 @@ class app_top_block(stdgui2.std_top_block, pubsub): self.src.set_iq_balance( correction ) if self._verbose: - print "Set IQ balance to", correction + print("Set IQ balance to", correction) except RuntimeError as ex: - print ex + print(ex) def set_sample_rate(self, samp_rate): samp_rate = self.src.set_sample_rate(samp_rate) if hasattr(self.scope, 'set_sample_rate'): self.scope.set_sample_rate(samp_rate) if self._verbose: - print "Set sample rate to:", samp_rate + print("Set sample rate to:", samp_rate) try: self[BWIDTH_KEY] = self.set_bandwidth(samp_rate) @@ -787,13 +787,13 @@ class app_top_block(stdgui2.std_top_block, pubsub): g = self[GAIN_RANGE_KEY(name)] gain = float(g.start()+g.stop())/2 if self._verbose: - print "Using auto-calculated mid-point gain" + print("Using auto-calculated mid-point gain") self[GAIN_KEY(name)] = gain return gain = self.src.set_gain(gain, name) if self._verbose: - print "Set " + name + " gain to:", gain + print("Set " + name + " gain to:", gain) def set_bandwidth(self, bw): clipped_bw = self[BWIDTH_RANGE_KEY].clip(bw) @@ -801,7 +801,7 @@ class app_top_block(stdgui2.std_top_block, pubsub): bw = self.src.set_bandwidth(clipped_bw) if self._verbose: - print "Set bandwidth to:", bw + print("Set bandwidth to:", bw) return bw @@ -814,7 +814,7 @@ class app_top_block(stdgui2.std_top_block, pubsub): f = self[FREQ_RANGE_KEY] freq = float(f.start()+f.stop())/2.0 if self._verbose: - print "Using auto-calculated mid-point frequency" + print("Using auto-calculated mid-point frequency") self[CENTER_FREQ_KEY] = freq return @@ -825,22 +825,22 @@ class app_top_block(stdgui2.std_top_block, pubsub): if freq is not None: if self._verbose: - print "Set center frequency to", freq + print("Set center frequency to", freq) elif self._verbose: - print "Failed to set freq." + print("Failed to set freq.") return freq def set_freq_corr(self, ppm): if ppm is None: ppm = 0.0 if self._verbose: - print "Using frequency corrrection of", ppm + print("Using frequency corrrection of", ppm) self[FREQ_CORR_KEY] = ppm return ppm = self.src.set_freq_corr(ppm) if self._verbose: - print "Set frequency correction to:", ppm + print("Set frequency correction to:", ppm) def main (): app = stdgui2.stdapp(app_top_block, "osmocom Spectrum Browser", nstatus=1) -- 2.24.0 From laforge at osmocom.org Mon Nov 11 13:29:37 2019 From: laforge at osmocom.org (Harald Welte) Date: Mon, 11 Nov 2019 14:29:37 +0100 Subject: [PATCH] build gr-iqbal w/ clang In-Reply-To: <0a4991d2-8051-4e8b-8f02-55b97a92f6e2@www.fastmail.com> References: <0a4991d2-8051-4e8b-8f02-55b97a92f6e2@www.fastmail.com> Message-ID: <20191111132937.GE25894@nataraja> Hi Brian, On Mon, Nov 11, 2019 at 01:16:11AM -0500, Brian Waters wrote: > Clang doesn't automatically define the "complex" keyword like old versions of GCC apparently used to. Appending this little check enabled compiling gr-iqbal w/ Clang, which is now the default compiler on OpenBSD and I think FreeBSD too. Thanks, applied. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at osmocom.org Mon Nov 11 13:29:12 2019 From: laforge at osmocom.org (Harald Welte) Date: Mon, 11 Nov 2019 14:29:12 +0100 Subject: Small patch to fix building librtlsdr on OpenBSD In-Reply-To: References: Message-ID: <20191111132912.GD25894@nataraja> Hi Brian, On Tue, Nov 05, 2019 at 05:05:47PM -0500, Brian Waters wrote: > Gets rid of librt, which doesn't exist on OpenBSD. The version of librtlsdr in the OpenBSD ports tree is extremely old (~2013), so this should help some users. thanks, applied. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From brian at brianmwaters.net Wed Nov 13 00:16:27 2019 From: brian at brianmwaters.net (Brian Waters) Date: Tue, 12 Nov 2019 19:16:27 -0500 Subject: Migrating gr-iqbal to Gnuradio 3.8 Message-ID: <5711f6c6-66f3-4e71-99e0-e3f7e562ed0e@www.fastmail.com> I just got an email from someone at RedHat; they seem to think that I am one of the gr-iqbal maintainers since I have the most recent commit ;). Apparently they have their own patch for Python 3 and Gnuradio 3.8, but wanted to know if upstream would be supporting the migration. Since I am not really upstream, I thought I'd forward the patch along. https://src.fedoraproject.org/rpms/gr-iqbal/blob/master/f/gr-iqbal-0.37.2-gnuradio38.patch -- Brian M. Waters brian at brianmwaters.net From 246tnt at gmail.com Wed Nov 13 07:59:48 2019 From: 246tnt at gmail.com (Sylvain Munaut) Date: Wed, 13 Nov 2019 08:59:48 +0100 Subject: Migrating gr-iqbal to Gnuradio 3.8 In-Reply-To: <5711f6c6-66f3-4e71-99e0-e3f7e562ed0e@www.fastmail.com> References: <5711f6c6-66f3-4e71-99e0-e3f7e562ed0e@www.fastmail.com> Message-ID: I have several patches pending already, but I have to review exactly what 3.8 build system change are really required and I haven't had the time to do that yet, other priorities ATM. I'll eventually get to it. Sylvain From cmrincon611 at hotmail.com Sat Nov 16 09:10:54 2019 From: cmrincon611 at hotmail.com (=?iso-8859-1?Q?C=E9sar_fumfum?=) Date: Sat, 16 Nov 2019 09:10:54 +0000 Subject: about gr-osmocom Message-ID: Hi, Im an engineering student and would love to see gr-osmosdr working again. Is there anyone working on gr-osmosdr at present? I'm thinking that it will be a great feature to work on, and i can try to help to maintiain the feature if you solve my doubts and my newbie errors. I don't think that this is a newbie to gnu dev task but i really would love to see gr-osmocom working again. C?sar. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cmrincon611 at hotmail.com Sat Nov 16 09:03:30 2019 From: cmrincon611 at hotmail.com (=?iso-8859-1?Q?C=E9sar_fumfum?=) Date: Sat, 16 Nov 2019 09:03:30 +0000 Subject: gr-osmosdr Message-ID: Hi, Im an engineering student and would love to see gr-osmosdr working again. Is there anyone working on gr-osmosdr at present? I'm thinking that it will be a great feature to work on, and i can try to help to maintiain the feature if you solve my doubts and my newbie errors. I don't think that this is a newbie to gnu dev task but i really would love to see gr-osmocom working again. C?sar. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cuervonicolas at gmail.com Sun Nov 24 10:39:26 2019 From: cuervonicolas at gmail.com (Nicolas Cuervo Benavides) Date: Sun, 24 Nov 2019 11:39:26 +0100 Subject: FOSDEM 2020: Free Software Radio Devroom CfP In-Reply-To: References: Message-ID: Dear friends and fans of software-defined radio, the SDR track at next year's FOSDEM still has some slots left! We already have some submissions and we are in the process of ranking those, but we will gladly add YOUR presentation to the list! If you have anything related to the field of free software radio, please head to: https://penta.fosdem.org/submission/FOSDEM20 and submit your short abstract! We're looking very much forward to your submission. For the committee, Nicolas Cuervo On Wed, Oct 16, 2019 at 8:19 PM Nicolas Cuervo Benavides < cuervonicolas at gmail.com> wrote: > Dear friends and fans of software-defined radio and free/open-source radio > topics in general, > > FOSDEM 2020 (the free and open-source developer's meeting in Brussels, > Europe) will, once again, feature a track on Software Defined Radio, and > any other radio-related topics in the (now known as) *Free Software Radio* devroom. > Therefore, we invite developers and users from the free software radio > community to join us for this track and present your talks or demos. > > > Software Radio has become an important tool to allow anyone to access the > EM spectrum. Using free software radio libraries and applications and cheap > hardware, anyone can now start hacking on wireless communications, remote > sensing, radar, fun hacks of all sorts, or other applications. At FOSDEM, > we hope to network all these projects and improve collaboration, bring new > ideas forward and get more people involved. > > > The track's web site resides at the link below. The final schedule will be > available through Pentabarf and the official FOSDEM website. > > https://fosdem.org/2020/schedule/track/free_software_radio/ > > > Additional Information will be also available at: > https://wiki.gnuradio.org/index.php/FOSDEM_2020 > > > ** Submit your presentations > > To suggest a talk, go to https://penta.fosdem.org/submission/FOSDEM20 and > follow the instructions (you need an account, but can use your account from > last year if you have one). You need to create an 'Event'; make sure it's > in the Free Software Radio track! Lengths aren't fixed, but give a > realistic estimate and please don't exceed 30 minutes unless you have > something special planned (in that case, contact one of us). Also, don't > forget to include time for Q&A. > We will typically go for 30-minute slots -- shorter talks, unless they're > really short, usually tend to screw up the schedule too much. > > You aren't limited to slide presentations, of course. Be creative. > However, FOSDEM is an open-source conference, therefore we ask you to stay > clear of marketing presentations and present something relevant to > free/open software. We like nitty-gritty technical stuff. > > Topics discussed in this devroom include: > > * SDR Frameworks + Tools > * Cellular/telecoms software > * Free/Open SDR hardware > * Wireless security > * Random fun wireless hacks > * SDR in education > * Satellite/spacecraft communication > * Ham radio related topics > > > ** Important Dates > > FOSDEM is February 1st and 2nd, 2020. The Free Software Radio devroom is > happening on Sunday, the 2nd of February. > > The submission deadline is Friday, December 6th. A complete schedule for > the presentations in the devroom will be available on the 15th of December. > > > In the last years we were always full to the brim with presentations, so > if you want to present, please make sure to submit your abstracts soon! > > ** Steering Committee > The track committee consists of: > > * Phil Balister - "Crofton" > * Sylvain Munaut -"tnt" > * Derek Kozel - "dkozel" > * Nicolas Cuervo - "primercuervo" > * Martin Braun - "mbr0wn" (Emeritus) > > > Hope to hear from you soon! And please forward this announcement. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Sat Nov 30 19:05:52 2019 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 30 Nov 2019 20:05:52 +0100 Subject: gr-fosphor install troubles:" Unable to share spectrum VBO into OpenCL context" openCL/GL sharing In-Reply-To: References: Message-ID: Hi Aaron, Finally got a chance to look at this in all details and : (1) indeed, removing that clear in deferred init fixes the issue (2) as you said, it's not even needed since the cl code will clear the buffers by itself. Looking at the code history, only the GL part had clear in the beginning and that wasn't enough in some cases and so later on I added CL clears and didn't remove the GL ones that had become redundant. Cheers, Sylvain