Re: [Discuss-gnuradio] hi all, can I use one RX receive a wideband signal and then seperate it to many narrowband signals
Martin, Thank u very much. But how much MHz is the limit in your word "a couple of MHz"? On Tue, Dec 21, 2010 at 6:19 PM, Martin Braun wrote: > On Tue, Dec 21, 2010 at 06:02:44PM +0800, James Jordan wrote: > > Hi all, I need to receive many narrowband signals, but usrp hard ware > only > > provide 4 RX, > > so I need to receive more than one narrowband signals per RX. Is my idea > > possible? > > I dont want to use more than one usrp to achieve that, anyway which will > be an > > option if my first idea can't work. > > If your total bandwidth (sum of all bandwidths) does not exceed a couple > of MHz, you can use the polyphase channelizer (pfb_channelizer_ccf). > The result will be an equally spaced set of narrowband channels. > > Happy DSP'ing, > MB > > -- > Karlsruhe Institute of Technology (KIT) > Communications Engineering Lab (CEL) > > Dipl.-Ing. Martin Braun > Research Associate > > Kaiserstraße 12 > Building 05.01 > 76131 Karlsruhe > > Phone: +49 721 608-3790 > Fax: +49 721 608-6071 > www.cel.kit.edu > > KIT -- University of the State of Baden-Württemberg and > National Laboratory of the Helmholtz Association > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] import qtgui error
I tried the code of 'Tutorial - Using the QT GUI Blocks in GNU Radio', but error occurred. Traceback (most recent call last): File "qt_basics.py", line 4, in from gnuradio.qtgui import qtgui File "/opt/gnuradio/3.3.0/lib/python2.6/site-packages/gnuradio/qtgui/qtgui.py", line 6, in import _qtgui ImportError: /opt/gnuradio/3.3.0/lib/libgnuradio-qtgui-3.3.0.so.0: undefined symbol: _ZN9QwtPicker5resetEv Who can tell me what is the problem? Thank you! ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] import qtgui error
2010/12/22 lishan_wh : > I tried the code of 'Tutorial - Using the QT GUI Blocks in GNU Radio', but > error occurred. > > Traceback (most recent call last): > File "qt_basics.py", line 4, in > from gnuradio.qtgui import qtgui > File > "/opt/gnuradio/3.3.0/lib/python2.6/site-packages/gnuradio/qtgui/qtgui.py", > line 6, in > import _qtgui > ImportError: /opt/gnuradio/3.3.0/lib/libgnuradio-qtgui-3.3.0.so.0: undefined > symbol: _ZN9QwtPicker5resetEv > > Who can tell me what is the problem? Thank you! What version of QWT are you using? What's your OS? Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] USRP2 and MIMO
I have questions about using MIMO on USRP2, and also debugging FPGA code on USRP2. I am not using UHD. 1. Connecting 2 USRPs with the MIMO cable: I am looking at the code for the mimo_tx firmware and do not see how control packets, say, setting frequency, interpolation, gain etc. are sent to the slave. The mimo_app_common_v2.c handle_control_chan_frame function seems to drop these packets right after handling them. The example code in usrp2/host/apps/test_mimo_tx.cc does not seem to do anything special either to deal with this, in fact, the code to set any board specific parameters is commented out. The mimo_tx_slave still has the handle_control_chan frame code in app_common_v2.c which it uses (not mimo_app_common). Does that mean the slave USRP also needs to be connected via ethernet, and one needs to get a handle via the usrp2::make interface separately to the master and slave to set control parameters (although the example code in usrp2/host/apps/test_mimo_tx does not do that)? 2. Debugging FPGA code on the USRP2: The USRP2 fpga space available is so small that I can't really effectively put chipscope on it. What debugging techniques or tools do you use to debug the FPGA code on the USRP2? Thanks, Arun ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and MIMO
On 12/22/2010 02:21 PM, Arun Pillai wrote: I have questions about using MIMO on USRP2, and also debugging FPGA code on USRP2. I am not using UHD. 1. Connecting 2 USRPs with the MIMO cable: I am looking at the code for the mimo_tx firmware and do not see how control packets, say, setting frequency, interpolation, gain etc. are sent to the slave. The mimo_app_common_v2.c handle_control_chan_frame function seems to drop these packets right after handling them. The example code in usrp2/host/apps/test_mimo_tx.cc does not seem to do anything special either to deal with this, in fact, the code to set any board specific parameters is commented out. The mimo_tx_slave still has the handle_control_chan frame code in app_common_v2.c which it uses (not mimo_app_common). Does that mean the slave USRP also needs to be connected via ethernet, and one needs to get a handle via the usrp2::make interface separately to the master and slave to set control parameters (although the example code in usrp2/host/apps/test_mimo_tx does not do that)? Those apps are old and should be deleted. To see how the MIMO cable is handled you will need to get the packet_router branch from the UHD repository. 2. Debugging FPGA code on the USRP2: The USRP2 fpga space available is so small that I can't really effectively put chipscope on it. What debugging techniques or tools do you use to debug the FPGA code on the USRP2? I never use Chipscope, but I know people have used it on the USRP2 in the past. I prefer to use the MICTOR logic analyzer connector, which gets you 34 pins. If you need more than that you can use the GPIOs on the daughterboads if you put BasicRX and BasicTX boards on. That gives you an extra 32 pins. Matt ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] [UHD] CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
I have compiled and run UHD code that was downloaded one day in last week. One problem was that "tx_timed_samples.cpp" does not work. The timing control didn't work. Even I give 10 secs delay, the code just promptly send samples without any delay. Whereas receiver properly wait for the specified time before starting the reception process. Therefore, I have updated UHD code today by - "git pull" in /root/git/uhd/ - "cmake ../" in /root/git/uhd/build got following error - -- Interface address discovery supported through getifaddrs. -- -- Configuring USRP1 support... -- USRP1 support configured automatically -- Enabling USRP1 support. -- -- Configuring USRP2 support... -- USRP2 support configured automatically -- Enabling USRP2 support. -- -- Configuring USRP-E100 support... -- USRP-E100 support configured automatically -- Disabling USRP-E100 support. -- -- Configuring priority scheduling... -- Performing Test HAVE_PTHREAD_SETSCHEDPARAM -- Performing Test HAVE_PTHREAD_SETSCHEDPARAM - Success -- Performing Test HAVE_WIN_SETTHREADPRIORITY -- Performing Test HAVE_WIN_SETTHREADPRIORITY - Failed -- Priority scheduling supported through pthread_setschedparam. -- -- Configuring module loading... -- Looking for C++ include dlfcn.h -- Looking for C++ include dlfcn.h - found -- Looking for C++ include windows.h -- Looking for C++ include windows.h - not found -- Module loading supported through dlopen. -- Local package data directory: /usr/local/share/uhd -- Installer package data directory: /usr/share/uhd -- -- ## -- # LibUHD enabled components -- ## -- * Examples -- * Utils -- * Tests -- * Doxygen -- * USB -- * USRP1 -- * USRP2 -- -- ## -- # LibUHD disabled components -- ## -- * Manual -- * USRP-E100 -- -- Using install prefix: /usr/local CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: LIBUSB_INCLUDE_DIR (ADVANCED) used as include directory in directory /root/git/uhd/host/lib LIBUSB_LIBRARIES (ADVANCED) linked by target "uhd" in directory /root/git/uhd/host/lib -- *From: Sangho Oh * *Voice mail: (609) 759-1552* ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re:Re: [Discuss-gnuradio] import qtgui error
Tom, I use Ubuntu 9.04 and QWT-5.0.2. Thank you! Ally At 2010-12-22 22:55:41，"Tom Rondeau" wrote: >2010/12/22 lishan_wh : >> I tried the code of 'Tutorial - Using the QT GUI Blocks in GNU Radio', but >> error occurred. >> >> Traceback (most recent call last): >> File "qt_basics.py", line 4, in >> from gnuradio.qtgui import qtgui >> File >> "/opt/gnuradio/3.3.0/lib/python2.6/site-packages/gnuradio/qtgui/qtgui.py", >> line 6, in >> import _qtgui >> ImportError: /opt/gnuradio/3.3.0/lib/libgnuradio-qtgui-3.3.0.so.0: undefined >> symbol: _ZN9QwtPicker5resetEv >> >> Who can tell me what is the problem? Thank you! > >What version of QWT are you using? What's your OS? > >Tom ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] [UHD] CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
On 12/22/2010 04:10 PM, Sangho Oh wrote: > I have compiled and run UHD code that was downloaded one day in last week. > One problem was that "tx_timed_samples.cpp" does not work. > The timing control didn't work. > Even I give 10 secs delay, the code just promptly send samples without any > delay. > Whereas receiver properly wait for the specified time before starting the > reception process. > Ok, thank you for the report. I will try to replicate the issue. > Therefore, I have updated UHD code today by > > - "git pull" in /root/git/uhd/ > - "cmake ../" in /root/git/uhd/build > > got following error > This was due to adding new components in the build. The problem has just been fixed. Update and do: rm CMakeCache.txt cmake ../ -josh > > - > -- Interface address discovery supported through getifaddrs. > > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] [UHD] CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
On 12/22/2010 04:10 PM, Sangho Oh wrote: > I have compiled and run UHD code that was downloaded one day in last week. > One problem was that "tx_timed_samples.cpp" does not work. > The timing control didn't work. > Even I give 10 secs delay, the code just promptly send samples without any > delay. > Whereas receiver properly wait for the specified time before starting the > reception process. > On this issue, you are probably sending a small number of samples which are completely consumed by the device. The example app does not wait for an end of burst acknowledgement so it exits before the samples are actually transmitted. Try setting --nsamps to a very large value (several seconds worth of samples) to prove that the send-timed is indeed functioning. -josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and MIMO
On 12/22/2010 5:33 PM, Matt Ettus wrote: On 12/22/2010 02:21 PM, Arun Pillai wrote: I have questions about using MIMO on USRP2, and also debugging FPGA code on USRP2. I am not using UHD. 1. Connecting 2 USRPs with the MIMO cable: I am looking at the code for the mimo_tx firmware and do not see how control packets, say, setting frequency, interpolation, gain etc. are sent to the slave. The mimo_app_common_v2.c handle_control_chan_frame function seems to drop these packets right after handling them. The example code in usrp2/host/apps/test_mimo_tx.cc does not seem to do anything special either to deal with this, in fact, the code to set any board specific parameters is commented out. The mimo_tx_slave still has the handle_control_chan frame code in app_common_v2.c which it uses (not mimo_app_common). Does that mean the slave USRP also needs to be connected via ethernet, and one needs to get a handle via the usrp2::make interface separately to the master and slave to set control parameters (although the example code in usrp2/host/apps/test_mimo_tx does not do that)? Those apps are old and should be deleted. To see how the MIMO cable is handled you will need to get the packet_router branch from the UHD repository. Thank you. Do I need to use ISE 12 to build this FPGA code? Is there a particular minor revision number that I need to use in 12? Arun ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and MIMO
> Thank you. Do I need to use ISE 12 to build this FPGA code? Is there a > particular minor revision number that I need to use in 12? > pre-built images here http://www.ettus.com/downloads/uhd_images/experimental/UHD-mimo-cable-support/ -josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Re: [USRP-users] UHD Announcement - December 13th 2010 - MIMO cable support
Is the FPGA code for mimo cable support available? Is that also on the packet_router branch (you mention only the host code below)? If not, how can I access it? Also, are there example host programs that exercise this code? Thanks, Arun On 12/13/2010 7:34 PM, Josh Blum wrote: Hello list, I would like to announce support for the MIMO cable with UHD. The support is experimental, so its not in the mainline yet, and is only available for USRP2 at the moment. The source for the FPGA code has not yet been pushed but you can get the pre-built images here: http://www.ettus.com/downloads/uhd_images/experimental/UHD-mimo-cable-support/ The supporting host code is available on the packet_router branch of the uhd repo: http://code.ettus.com/redmine/ettus/projects/uhd/repository/show?rev=packet_router Here is an excerpt from the docs on the MIMO cable in UHD: MIMO cable configuration Using the MIMO cable, two USRP devices can be grouped together in a multi-device configuration. Only one device in the configuration can be attached to the ethernet. This device will be referred to as the master, and the other device, the slave. * The master provides reference clock and time synchronization to the slave. * All data passing between the host and the slave is routed over the MIMO cable. * Both master and slave must have different IPv4 addresses but in the same subnet. * The master and slave may be used individually or in a multi-device configuration. I hope that explains it. Feedback is welcome! Thanks, -Josh ___ USRP-users mailing list usrp-us...@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] USRP2 and MIMO
I actually need to modify the FPGA source to add functionality to it. Is the source available? Thanks. On 12/22/2010 8:07 PM, Josh Blum wrote: Thank you. Do I need to use ISE 12 to build this FPGA code? Is there a particular minor revision number that I need to use in 12? pre-built images here http://www.ettus.com/downloads/uhd_images/experimental/UHD-mimo-cable-support/ -josh ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] SWIG, shared pointers and inheritance.
I'm having trouble with SWIG, shared pointers, and inheritance.
I'm trying to create a base gr_constellation class, which would be a
helper object for
doing QAM-like modulations. It would contain a list of the
constellation points, and
a decision_maker function for demodulation. To implement different
QAM-like modulations you
would subclass gr_constellation.
I thought I should try to use shared pointers for the gr_constellation
objects (since that's what's used
for the blocks and presumably there are good reasons). I can get
everything working fine
until I subclass gr_constellation and then pass a shared pointer to
the subclass to a function expecting
the parent shared pointer object.
i.e. B is a subclass of A
sA is a shared pointer to A
sB is a shared pointer to B
f(sA) is a function expecting a shared pointer to A
If I pass sB to f() then an error is raised.
This error only occurs at the python level.
At the C++ level I can pass sB to f() without a problem.
This problem appears to have been solved in gnuradio already, since
the connect functions accept a shared
pointer to any of the blocks. However, I haven't been able to work
out how it's done. Does anyone know
how to do this? I thought perhaps gr_basic_block::basic_block() has
something to do with this but
haven't been able to track it down.
I'm now including the contents of a few files that reproduce this
problem independently of gnuradio, although
they require the gr_shared_ptr.i file.
To compile I run:
swig -c++ -python -Iboost blah.i
python setup.py build_ext --inplace
And then test with:
python test.py
Cheers,
Ben
---blah.h
#ifndef INCLUDED_BLAH_H
#define INCLUDED_BLAH_H
#include
class Blah {};
class Bloop : public Blah {};
typedef boost::shared_ptr blah_sptr;
typedef boost::shared_ptr bloop_sptr;
void do_something (blah_sptr bls);
blah_sptr make_blah();
bloop_sptr make_bloop();
#endif
---blah.cc---
#include
#include "blah.h"
void do_something (blah_sptr bls)
{
std::cout << "Doing something." << std::endl;
}
blah_sptr make_blah() { return blah_sptr(new Blah ()); };
bloop_sptr make_bloop() { return bloop_sptr(new Bloop ()); };
---blah.i
%module(docstring="
This module does nothing useful.
") blah
%{
#include "blah.h"
%}
%include
%include
%template(blah_sptr) boost::shared_ptr;
%template(bloop_sptr) boost::shared_ptr;
---setup.py
"""
setup.py file for SWIG example
"""
from distutils.core import setup, Extension
blah_module = Extension('_blah',
include_dirs = ['/usr/include/boost'],
sources=['blah_wrap.cxx', 'blah.cc'],
)
setup (name = 'blah',
version = '0.1',
author = "SWIG Docs",
description = """Simple swig example""",
ext_modules = [blah_module],
py_modules = ["blah"],
)
---test.py-
import blah
bla = blah.make_blah()
blp = blah.make_bloop()
# Works fine.
blah.do_something(bla)
# Fails with "TypeError: in method 'do_something', argument 1 of type
'blah_sptr'"
blah.do_something(blp)
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] hi all, can I use one RX receive a wideband signal and then seperate it to many narrowband signals
Hi Martin, pfb_channelizer_ccf will seperate all channels, But I dont need each channel. I only need the channel I am interested in. Seperating all channels will eat a lot of CPU resource. I have check pfb_channelizer_ccf source, it finally use fftw to process channelizer. So can I directly use fftw to do my work. On Tue, Dec 21, 2010 at 6:19 PM, Martin Braun wrote: > On Tue, Dec 21, 2010 at 06:02:44PM +0800, James Jordan wrote: > > Hi all, I need to receive many narrowband signals, but usrp hard ware > only > > provide 4 RX, > > so I need to receive more than one narrowband signals per RX. Is my idea > > possible? > > I dont want to use more than one usrp to achieve that, anyway which will > be an > > option if my first idea can't work. > > If your total bandwidth (sum of all bandwidths) does not exceed a couple > of MHz, you can use the polyphase channelizer (pfb_channelizer_ccf). > The result will be an equally spaced set of narrowband channels. > > Happy DSP'ing, > MB > > -- > Karlsruhe Institute of Technology (KIT) > Communications Engineering Lab (CEL) > > Dipl.-Ing. Martin Braun > Research Associate > > Kaiserstraße 12 > Building 05.01 > 76131 Karlsruhe > > Phone: +49 721 608-3790 > Fax: +49 721 608-6071 > www.cel.kit.edu > > KIT -- University of the State of Baden-Württemberg and > National Laboratory of the Helmholtz Association > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Help required --Urgent--LED
-- View this message in context: http://old.nabble.com/Help-required---Urgent--LED-tp30519902p30519902.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] hi all, can I use one RX receive a wideband signal and then seperate it to many narrowband signals
On Thu, Dec 23, 2010 at 1:19 AM, James Jordan wrote: > Hi Martin, > pfb_channelizer_ccf will seperate all channels, But I dont need each > channel. > I only need the channel I am interested in. Seperating all channels will eat > a lot of CPU resource. Not really. It's a very efficient algorithm and won't cost you that much. > I have check pfb_channelizer_ccf source, it finally use fftw to process > channelizer. > So can I directly use fftw to do my work. Not quite. The PFB channelizer uses a filterbank where each filter is specifically generated with a phase relation. The FFT part isn't doing exactly what you expect it's doing. We'd have to go through the math, though. If you are looking to just get a single channel out, then use the pfb_decimator_ccf(N, taps, channel) to split the bandwidth into "N" channels, using filter taps "taps," and you can specify which channel you want to take by specifying the "channel." Here's the way to translate the "channel" into the physical Nyquist zone you are looking for N=7 (hopefully this format survives): Channel: 456 0 1 2 3 Frequency: -3B | -2B | -1B | 0 | 2B | 2B | 3B Tom > On Tue, Dec 21, 2010 at 6:19 PM, Martin Braun wrote: >> >> On Tue, Dec 21, 2010 at 06:02:44PM +0800, James Jordan wrote: >> > Hi all, I need to receive many narrowband signals, but usrp hard ware >> > only >> > provide 4 RX, >> > so I need to receive more than one narrowband signals per RX. Is my idea >> > possible? >> > I dont want to use more than one usrp to achieve that, anyway which will >> > be an >> > option if my first idea can't work. >> >> If your total bandwidth (sum of all bandwidths) does not exceed a couple >> of MHz, you can use the polyphase channelizer (pfb_channelizer_ccf). >> The result will be an equally spaced set of narrowband channels. >> >> Happy DSP'ing, >> MB >> >> -- >> Karlsruhe Institute of Technology (KIT) >> Communications Engineering Lab (CEL) >> >> Dipl.-Ing. Martin Braun >> Research Associate >> >> Kaiserstraße 12 >> Building 05.01 >> 76131 Karlsruhe >> >> Phone: +49 721 608-3790 >> Fax: +49 721 608-6071 >> www.cel.kit.edu >> >> KIT -- University of the State of Baden-Württemberg and >> National Laboratory of the Helmholtz Association >> >> >> ___ >> Discuss-gnuradio mailing list >> Discuss-gnuradio@gnu.org >> http://lists.gnu.org/mailman/listinfo/discuss-gnuradio >> > > > ___ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > http://lists.gnu.org/mailman/listinfo/discuss-gnuradio > > ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
[Discuss-gnuradio] Help required --Urgent--F led light glowing and D led light is not glowing
Hi When I port the firmware and the u2_rev3.bin downloaded from the repository everything works fine. But when i compile the usrp2 code (successful compilation) and I port it with my firmware, there is a problem. The problem is the F led light glows and the D led light does not glow. I am using ISE 12.3 version and the size of the u2_rev.bin is 842.4 kb. -- View this message in context: http://old.nabble.com/Help-required---Urgent--F-led-light-glowing-and-D-led-light-is-not-glowing-tp30519931p30519931.html Sent from the GnuRadio mailing list archive at Nabble.com. ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
