# FPGA mo

**URL:** <https://www.ruby-forum.com/t/fpga-mo/207582>\
**Category:** GNU Radio\
**Created:** [May 28, 2011, 6:57pm UTC](https://www.ruby-forum.com/t/fpga-mo/207582 "2011-05-28T18:57:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [May 28, 2011, 6:57pm UTC](https://www.ruby-forum.com/t/fpga-mo/207582/1 "2011-05-28T18:57:11Z")

</div>

Hi all,

I’m not sure whether to post this to GnuRadio or to USRP-users, so I  
post it here.

We’ve started a project to implement a custom SDR hardware (which we  
plan to open-source later) and we want to reuse as much of USRP FPGA  
code as possible. But it will require a good deal of customization as  
well.

So, we’re looking for an advice on how to structure our relations with  
the upstream (i.e. GnuRadio/USRP) the best way. I.e. where should we  
place our code and how to ensure our code will be accepted to the  
mainline, etc?

–  
Regards,  
Alexander C…

---

<div class="post-metadata">

**Author:** ![alcost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4da419/32.png) [@alcost](https://www.ruby-forum.com/u/alcost)\
**Post date:** [May 28, 2011, 7:05pm UTC](https://www.ruby-forum.com/t/fpga-mo/207582/2 "2011-05-28T19:05:13Z")

</div>

> So, we’re looking for an advice on how to structure our relations with  
> the upstream (i.e. GnuRadio/USRP) the best way. I.e. where should we  
> place our code and how to ensure our code will be accepted to the  
> mainline, etc?

I can’t answer the questions about where to best place the code in the  
tree, but maintaining compatibility with the  
UHD wire protocol and API would really help make it easy to integrate  
into Gnu Radio. Matt can comment on  
UHD licensing for projects like this, I’m sure.

–  
Marcus L.  
Principal Investigator  
Shirleys Bay Radio Astronomy Consortium

> **[Live Draw HK Tercepat | Result HK | HK Pools | Live HK | HK Prize Hari Ini](https://www.sbrac.org/)**
>
> Temukan live draw hk tercepat melalui halaman hk pools yang resmi dan dapatkan result hk prize melalui live hk secara langsung di situs kami.

---

<div class="post-metadata">

**Author:** ![alcost](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4da419/32.png) [@alcost](https://www.ruby-forum.com/u/alcost)\
**Post date:** [May 28, 2011, 7:31pm UTC](https://www.ruby-forum.com/t/fpga-mo/207582/3 "2011-05-28T19:31:48Z")

</div>

On Sat, May 28, 2011 at 21:04, Marcus D. Leech [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> > So, we’re looking for an advice on how to structure our relations with  
> > the upstream (i.e. GnuRadio/USRP) the best way. I.e. where should we  
> > place our code and how to ensure our code will be accepted to the  
> > mainline, etc?
> 
> I can’t answer the questions about where to best place the code in the tree,  
> but maintaining compatibility with the  
> UHD wire protocol and API would really help make it easy to integrate into  
> Gnu Radio. Matt can comment on  
> UHD licensing for projects like this, I’m sure.

To make it more clear - we intend to keep all VRT/UHD related FPGA  
code in place and just replace/change interaction with RF part. May be  
we’ll have to slightly extend VRT/UHD code for our specific purposes,  
but it will be minor changes.

In other words - all our changes will be to support a new platform  
seamlessly with existing UHD code.

–  
Regards,  
Alexander C..