On Sat, May 28, 2011 at 21:30, Alexander C. [email protected] wrote:
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.
Could anyone comment on this topic after all?
Tom, Josh, Philip - I’m not sure who should I bug about this?
PS I’ve changed subject to a more meaningful. Sorry for messed subject
line in the original e-mail.
I can’t answer the questions about where to best place the code in the tree,
In other words - all our changes will be to support a new platform
seamlessly with existing UHD code.
Could anyone comment on this topic after all?
Tom, Josh, Philip - I’m not sure who should I bug about this?
We are always looking for contributions to the FPGA code and will
consider including any interesting new functionality.
Is a new platform considered as an interesting functionality?
And the main question - is there any guideline on how to add a new
platform so that it will be possible to mainline it?
On Thu, Jun 9, 2011 at 2:01 PM, Alexander C. < [email protected]> wrote:
I’m not sure whether to post this to GnuRadio or to USRP-users, so I
place our code and how to ensure our code will be accepted to the
To make it more clear - we intend to keep all VRT/UHD related FPGA
We are always looking for contributions to the FPGA code and will
consider including any interesting new functionality.
Is a new platform considered as an interesting functionality?
And the main question - is there any guideline on how to add a new
platform so that it will be possible to mainline it?
–
Regards,
Alexander C…
As for where to put it, if it’s all being done open source, a service
like
github is great for this sort of thing. It makes it easy to track your
changes and for everyone to see what’s going on. Then, it’s easy for us
to
take the code in afterwards. Since they provide the management and
infrastructure as their business model, it’s a win for all of us.
As for where to put it, if it’s all being done open source, a service like
github is great for this sort of thing. It makes it easy to track your
changes and for everyone to see what’s going on. Then, it’s easy for us to
take the code in afterwards. Since they provide the management and
infrastructure as their business model, it’s a win for all of us.
Yes, I know about github and that’s what we intend to use indeed.
My question was more about where to put the code with respect to
source code directory tree. But seems like there are no guidelines, so
we’ll go the way we find convenient for us.
–
Regards,
Alexander C…
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.