Libusrp/libusrp2 vs uhd plans

As Ettus R. has announced the UHD software support for USRP1 and
USRP2 is stabilizing. There are many long awaited features that will
become part of this next generation code, and the question has come up
about the future of the current GNU Radio support for this hardware.

We will address this in three stages.

Firstly, the current libusrp/libusrp2/gr-usrp/gr-usrp2 components will
become part of the 3.3 stable release series. This is intended as a
measure to support existing user code that depends on this
functionality, and we will maintain this with bug fixes as needed.
The GNU Radio release tarballs will include the host and firmware
code, and the gnuradio.org website will host binaries for the
associated FPGA image and firmware images. The corresponding FPGA
source code will continue to be hosted/distributed by Ettus R…
This gives long-term support for existing users who do not plan to
upgrade.

Secondly, during the 3.4 development series, we will incorporate the
gr-uhd GNU Radio host code blocks, and begin transitioning our
examples, demos, and other code that uses gr-usrp/gr-usrp2 to use
gr-uhd instead. This will be gated by available
functionality/stability of the Ettus R. code.

Finally, also during the 3.4 development series, we will extract the
libusrp/libusrp2 code (but not gr-usrp or gr-usrp2) into its own
stand-alone distribution and remove it from GNU Radio proper. This
will give developers the choice of installing the “FSF” version of the
libraries or the Ettus R. libraries (or both) as desired, and
GNU Radio will install gr-usrp/gr-usrp2 and/or gr-uhd depending on
what was detected during configuration.

It is intended that as of stable series 3.4, future GNU Radio
development will continue around the Ettus R. UHD code features,
and only critical bug fixes in the stand-alone FSF library be
considered.

Please feel free to respond with any questions/concerns.

Johnathan C.

Johnathan or Matt

Do we have any details on licensing of the UHD?
You mentioned full FSF only for libusrp. Will UHD be closed source?

Charles

On Mon, Apr 26, 2010 at 2:17 PM, Johnathan C.

On 04/26/2010 12:16 PM, Charles H. wrote:

Johnathan or Matt

Do we have any details on licensing of the UHD?
You mentioned full FSF only for libusrp. Will UHD be closed source?

No. As stated in the past, UHD will be dual licensed. Option 1 is GPL.
So it works fine with GNU Radio or OpenBTS, etc., and could even be
used with other people’s hardware as long as it is used in compliance
with GPL.

For option 2 we have not yet finalized the wording, but the intention is
to enable it to be used with any other software you like as long as it
is used with Ettus R. hardware.

Matt

On Mon, Apr 26, 2010 at 12:16, Charles H. [email protected]
wrote:

Do we have any details on licensing of the UHD?
You mentioned full FSF only for libusrp. Will UHD be closed source?

I’ll answer this briefly now in case Matt doesn’t see this for a
while, though I can’t speak for Ettus R…

In short, UHD will be copyright Ettus R. and licensed for use
using GPL (I don’t think the GPL version number has been announced).
In addition, it will also be available for licensing to third parties
with non-GPL licenses for use in environments besides GNU Radio. The
source code in its current state has already been published as a git
repository.

Johnathan

The UHD is open source, licensed under GPLv3

See the wiki to get the source code:
http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/wiki

And the license:
http://ettus-apps.sourcerepo.com/redmine/ettus/projects/uhd/repository/revisions/master/entry/host/LICENSE

-Josh

Thank you so much for the quick reply.
Just to add: The LICENSE file on the git repository states GPL v3.

Perhaps I should have made the question a bit clearer: my concern was
over the future releases of it, and Matt has nailed it.
Really happy to see the way things are being conducted.
Cheers :slight_smile:

Charles

On Mon, Apr 26, 2010 at 4:27 PM, Johnathan C.

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs