|
From: | Jeff Fifield |
Subject: | Re: [Discuss-gnuradio] Re: gnuradio flowgraph mechanism |
Date: | Thu, 16 Feb 2006 16:08:40 -0700 |
User-agent: | Debian Thunderbird 1.0.7 (X11/20051017) |
Greg Troxel wrote:
After further thought, the simplest way to glue them together is to just use unix-domain datagram sockets or other IPC. This takes about 5 lines of Python on the GNU Radio end. At BBN we're planning to have some sort of integration between Click and GNU Radio (to do data networking with Click as the router and GNU Radio as the PHY, and the MAC somewhere TBD in between), and are heading for multiple processes and IPC exactly as Eric suggests. This also avoids having to figure out if the Click license is GPL compatible and requiring one's changes to Click to be under the GPL rather than the BSD/X11-like Click license. More importantly, it avoids difficult and hard to maintain cross-project software dependencies.
A year or two ago I made a shared memory ring buffer thing to let user level click and kernel level click talk to each other. Later I wrote some gnu radio code to talk to kernel click over the same interface.
The click code is available via subversion here: https://systems.cs.colorado.edu/svn/userclick There were some changes to linux internals that broke this recently but I know it works with slightly older kernels, for example 2.6.11.6. I have a newer version somewhere that I should find and check in...
The gsr code using the click interface is here: http://systems.cs.colorado.edu/~fifield/gsr_click.tar.gz This produces and consumes gr_messages.
-jf
[Prev in Thread] | Current Thread | [Next in Thread] |