Jeffery,

The first thing to keep in mind is that everything is GPL'ed (and
specifically, *not* LGPL).  This means that if you use any UHD host code,
you must obey the GPL for EVERYTHING that links in.  This goes all the way
up to your customer's application.  This restriction already applies for GNU
Radio itself since it is also GPL'ed.

The firmware is GPL'ed.  This means that if you use any of the firmware,
your ENTIRE firmware image must obey the terms of the GPL.

The FPGA design is GPL'ed.  This means that if you use any of our Verilog,
*everything* compiled into that FPGA image must comply with the GPL.  This
would include all of your custom signal processing code, if it is in the
same FPGA.

The implementation of UHD host code is heavily oriented towards the state
machines in the firmware and FPGA, so modifying it to work with other
devices is easier if they use the same firmware and FPGA designs.  This is
fine as long as you are ok with invoking the GPL requirements on those
portions of your design.

Users of Ettus Research hardware are able to use all of this under less
restrictive terms in our alternative license.

Matt Ettus
President, Ettus Research LLC


On Wed, Aug 24, 2011 at 8:23 AM, Wilson, Jeffery (DS-1) <jawil...@drs-ds.com
> wrote:

> Designation: Non-SSA/Finmeccanica
>
> Hello,****
>
> ** **
>
> We make several RF front-ends that we’d like to see supported in GNU Radio.
> Our initial idea is was to extend the Ettus UHD to include support for our
> devices, so that a waveform/flow graph using a UHD block could run using
> either a USRP or one of our devices with only minor modifications. Does it
> “make sense” to extend UHD for this purpose?****
>
> ** **
>
> Our radios are embedded Linux systems that can communicate over USB as well
> as Ethernet. Initially I would like to use Ethernet as communication (using
> sockets). As far as I can figure a good place to start would be to follow
> the USRP2 UHD implementation and re-implement it for our system.****
>
> ** **
>
> Any tips, examples or general guidance would be very much appreciated.****
>
> ** **
>
> Thank you!****
>
> ** **
>
> --****
>
> Jeff Wilson****
>
> DRS Signal Solutions, Inc.****
>
> Direct: 301.944.8772****
>
> ** **
>
> 3.1.1001
>
> _______________________________________________
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to