From leif at sm5bsz.com Fri Sep 2 03:11:11 2016 From: leif at sm5bsz.com (Leif Asbrink) Date: Fri, 2 Sep 2016 05:11:11 +0200 Subject: Raspberry Pi 2B In-Reply-To: <53C26C10.2040601@pabigot.com> References: <53C25D09.6040009@pabigot.com> <20140713105929.14427.qmail@stuge.se> <53C26C10.2040601@pabigot.com> Message-ID: <20160902051111.ab001e882479c6373a3543ad@sm5bsz.com> Hi All, This video shows that one can run a rtlsdr at 2.4 MHz on a Raspberry Pi 2B. Maybe interesting for portable use. https://www.youtube.com/watch?v=qGZmD8O4Flk Regards Leif From lucas at teske.net.br Fri Sep 2 03:16:20 2016 From: lucas at teske.net.br (Lucas Teske) Date: Fri, 2 Sep 2016 00:16:20 -0300 Subject: Raspberry Pi 2B In-Reply-To: <20160902051111.ab001e882479c6373a3543ad@sm5bsz.com> References: <53C25D09.6040009@pabigot.com> <20140713105929.14427.qmail@stuge.se> <53C26C10.2040601@pabigot.com> <20160902051111.ab001e882479c6373a3543ad@sm5bsz.com> Message-ID: <5ad695cc-7b8c-3ff9-a459-601d7406013f@teske.net.br> Hi Leif, I don't see why the rtlsdr wouldnt run at Raspberry PI. And probably it will run better at 2.56 Msps than 2.4Msps. Lucas On 02/09/2016 00:11, Leif Asbrink wrote: > Hi All, > > This video shows that one can run a rtlsdr at 2.4 MHz on a > Raspberry Pi 2B. Maybe interesting for portable use. > https://www.youtube.com/watch?v=qGZmD8O4Flk > > Regards > > Leif > > From nkcyham at yahoo.com Fri Sep 2 07:06:39 2016 From: nkcyham at yahoo.com (Neoklis Kyriazis) Date: Fri, 2 Sep 2016 07:06:39 +0000 (UTC) Subject: Help needed with DSP filter problems References: <44556526.308513.1472799999052.ref@mail.yahoo.com> Message-ID: <44556526.308513.1472799999052@mail.yahoo.com> Hi I have been experimenting writing DSP software, using librtlsdr and a NESDR dongle from NooElec. After much searching the Internet for code to design and implement DSP filters (with little success), I remembered that years ago I bought the "Digital Signal Processing" book by Steven W. Smith. I used the BASIC software included to produce C code to calculate the a and b coefficients for Low Pass or High Pass Chebyshev filters, from 2-pole to 20-pole if needed. Unfortunately, the cut-off frequency for a 6-pole Low Pass filter I implemented turns out to be 2x the required value, even though the design function that calculates the a and b coefficients produces values that match exactly values tabled in the book. This leaves me I think with the following possibilities: 1. That the calculated a and b coefficients are correct but my own code implementing a recursive filter is incorrect. 2. That I have incorporated the LPF filter function into my librtlsdr-based application incorrectly, perhaps misunderstanding parameters like the sampling rate or the required bandwidth. 3. That both the above implementations are correct but the BASIC code included in the book has a bug somewhere, so that both my own results for a and b and those tabled in the book are incorrect. Rather unlikely I thought.... So I am asking for help here from more knowledgeable DSP'ers hoping to resolve this matter, as the above mentioned book is very good, with very clear and simplified teaching of DSP for engineers _and_ it includes source code in BASIC for most of the algorithms it teaches. And it is available openly on the Internet with source code here!: http://dspguide.com/ My own GPL'ed application is available for inspection here: www.5b4az.org/pkg/sdrx/sdrx-0.3-beta.tar.bz2 The filter functions are in src/filters.c and SDR functions in src/rtlsdr.c My thanks here in advance! -- Best Regards Neoklis - Ham Radio Call:5B4AZ http://www.5b4az.org/ From laforge at gnumonks.org Sat Sep 24 12:31:59 2016 From: laforge at gnumonks.org (Harald Welte) Date: Sat, 24 Sep 2016 20:31:59 +0800 Subject: Moving from trac to a single redmine In-Reply-To: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> Message-ID: <20160924123159.sdqpnz5yksr6njcr@nataraja> Dear all, It's been more than half a year that we transitioned the Osmocom projects from the various trac instances to redmine. Still, a lot of people end up on the old redmine pages. How do I know? Because of the amount of personal e-mail I receive from people asking for accounts or for modification of the content there. [This is of course just the indicator, I don't mind those mails]. But what worries me is that people are looking at outdated information in the old trac without even knowing. How do we proceed about that? I'm not quite clear. The first step could be to add some kind of banner to the old trac installations, indicating at the header / footer of every page (or even as a floating block visible at all times) that this is old, outdated content that is scheduled to be removed at a certain date, and indicating the top-level page for the specific project in the osmocom.org redmine as an updated source. After that grace period has passed, we should probably make all the old trac pages redirect to the entry-page of the project in redmine. Trying to link to the respective new page in each individual wiki would be overly complicated and take a lot of time, unless somebody masocistic enough would volunteer for creating such a list. It can probably be auto-generated to some extent, but then each individual item would need to be manually verified and fixed up, if needed. Do you have other ideas on how to proceed in a better way? Do we have any volunters about any of the above? I'm quite sure it wouldbe easy to provide volunteers witha copy of the existing trac databases or any other information that might be needed. Thanks in advance for any assistance, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From holger at freyther.de Sat Sep 24 12:57:57 2016 From: holger at freyther.de (Holger Freyther) Date: Sat, 24 Sep 2016 14:57:57 +0200 Subject: Moving from trac to a single redmine In-Reply-To: <20160924123159.sdqpnz5yksr6njcr@nataraja> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> <20160924123159.sdqpnz5yksr6njcr@nataraja> Message-ID: <32B40E35-7B65-4478-ADCE-CD7771DDCA7B@freyther.de> > On 24 Sep 2016, at 14:31, Harald Welte wrote: > > Dear all, > > Still, a lot of people end up on the old redmine pages. How do I know? > Because of the amount of personal e-mail I receive from people asking > for accounts or for modification of the content there. eek. > > How do we proceed about that? I'm not quite clear. The first step > could be to add some kind of banner to the old trac installations, > indicating at the header / footer of every page (or even as a floating > block visible at all times) that this is old, outdated content that is > scheduled to be removed at a certain date, and indicating the top-level > page for the specific project in the osmocom.org redmine as an updated > source. After that grace period has passed, we should probably make all > the old trac pages redirect to the entry-page of the project in redmine. > > Trying to link to the respective new page in each individual wiki would > be overly complicated and take a lot of time, unless somebody masocistic > enough would volunteer for creating such a list. It can probably be > auto-generated to some extent, but then each individual item would need > to be manually verified and fixed up, if needed. > > Do you have other ideas on how to proceed in a better way? * banner to say to look at our redmine * disallow search engines to index trac (if that is still allowed) * not modify trac sites but use redirect of nginx > Do we have any volunters about any of the above? I'm quite sure it > wouldbe easy to provide volunteers witha copy of the existing trac > databases or any other information that might be needed. We can provide the access logs (all IP addresses point to the frontend server so we only show user agent that might be private). holger From 246tnt at gmail.com Sat Sep 24 14:01:52 2016 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 24 Sep 2016 08:01:52 -0600 Subject: Moving from trac to a single redmine In-Reply-To: <32B40E35-7B65-4478-ADCE-CD7771DDCA7B@freyther.de> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> <20160924123159.sdqpnz5yksr6njcr@nataraja> <32B40E35-7B65-4478-ADCE-CD7771DDCA7B@freyther.de> Message-ID: Hi, > * not modify trac sites but use redirect of nginx I've just put this in place for 'openbsc.osmocom.org' : rewrite ^/trac/wiki/(.*)/(.*)$ $scheme://osmocom.org/projects/openbsc/wiki/$1$2 redirect; rewrite ^/trac/wiki(.*)$ $scheme://osmocom.org/projects/openbsc/wiki$1 redirect; This seems to work fairly well. I'm sure there are some exceptions to those regexps, but I couldn't find any immediately. If we uncover them we can try to tweak them or just handle them manually. I've set them to temporary (302) redirects for now. Once we're a little more confident that this works well, this can be changed to 301s and extended to all the other old domains. If you find any case where those fails, please report. Cheers, Sylvain From laforge at gnumonks.org Mon Sep 26 01:11:08 2016 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 26 Sep 2016 09:11:08 +0800 Subject: Moving from trac to a single redmine In-Reply-To: <20160925155410.GA1868@dub7> References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> <20160924123159.sdqpnz5yksr6njcr@nataraja> <32B40E35-7B65-4478-ADCE-CD7771DDCA7B@freyther.de> <20160925155410.GA1868@dub7> Message-ID: <20160926011108.mxmktwgpty2ognob@nataraja> On Sun, Sep 25, 2016 at 05:54:10PM +0200, Neels Hofmeyr wrote: > On Sat, Sep 24, 2016 at 08:01:52AM -0600, Sylvain Munaut wrote: > > I've just put this in place for 'openbsc.osmocom.org' : > > > > rewrite ^/trac/wiki/(.*)/(.*)$ > > $scheme://osmocom.org/projects/openbsc/wiki/$1$2 redirect; > > rewrite ^/trac/wiki(.*)$ $scheme://osmocom.org/projects/openbsc/wiki$1 redirect; > > But so far the idea is to keep the trac online and browsable, right? the main problem is that search engines still primarily seem to index + link to the old trac instances. So we were keeping that alive for some time. However, as the content is going out of date, and people still show an interest in editing the old content, I think we need to switch the trac off soon and replace it with links to the redmine, even if it just links to the redmine entry page of that project. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From craig_comstock at yahoo.com Sun Sep 25 13:22:23 2016 From: craig_comstock at yahoo.com (Craig Comstock) Date: Sun, 25 Sep 2016 13:22:23 +0000 (UTC) Subject: Moving from trac to a single redmine In-Reply-To: References: <29DF7E51-8366-40A3-8EF1-F4705D3A0E6D@freyther.de> <20160924123159.sdqpnz5yksr6njcr@nataraja> <32B40E35-7B65-4478-ADCE-CD7771DDCA7B@freyther.de> Message-ID: <53112477.360510.1474809743413@mail.yahoo.com> I am working on fernvale-nuttx-bb (fernvale-nuttx + gnutoo's nuttx-bb) and wanted to check the osmocom bb on nuttx-bb. It seems all the links are broken in the redmine version of things and the trac URLs redirect to redmine so the content is "gone"? Can you help me resurrect pages like http://osmocom.org/projects/baseband/wiki/Nuttx-bbcompile?parent=Nuttx-bb Thanks,Craig From: Sylvain Munaut <246tnt at gmail.com> To: Holger Freyther Cc: "osmocom-sdr at lists.osmocom.org" ; baseband-devel ; OpenBSC Mailing List ; gmr at lists.osmocom.org Sent: Saturday, September 24, 2016 9:01 AM Subject: Re: Moving from trac to a single redmine Hi, > * not modify trac sites but use redirect of nginx I've just put this in place for 'openbsc.osmocom.org' : rewrite ^/trac/wiki/(.*)/(.*)$ $scheme://osmocom.org/projects/openbsc/wiki/$1$2 redirect; rewrite ^/trac/wiki(.*)$ $scheme://osmocom.org/projects/openbsc/wiki$1 redirect; This seems to work fairly well. I'm sure there are some exceptions to those regexps, but I couldn't find any immediately. If we uncover them we can try to tweak them or just handle them manually. I've set them to temporary (302) redirects for now. Once we're a little more confident that this works well, this can be changed to 301s and extended to all the other old domains. If you find any case where those fails, please report. Cheers, ? ? Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: