[USRP-users] Methodology for new NOC_IDs?

Jonathon Pendlum jonathon.pendlum at ettus.com
Mon Jul 13 18:44:19 EDT 2015

Hi Jason,

You didn't miss any documentation. NOC ID assignment does not have a formal
methodology and are assigned by the block's creator. Setting aside a
section for user blocks sounds like a good idea. For now feel free to set
your NOC IDs however you wish.


On Mon, Jul 13, 2015 at 8:07 AM, Jason Matusiak via USRP-users <
usrp-users at lists.ettus.com> wrote:

> I was wondering if there was a methodology or plan for how to pick new
> RFNoC ID values?  There are only a handful of values in place right now,
> so picking a new one is easy, but I imagine that it will start to get
> confusing as more and more blocks are added.
> Is there a thought to set aside a section for custom user blocks that
> aren't getting added into mainline?
> Also, have you been picking values to mean something (like certain
> ranges imply streaming, other imply using a Xilinx core, etc)?
> I am guessing that right now, things are just sort of picked based on
> who designed them, but I wanted to make sure I didn't miss documentation
> somewhere that spelled out an overarching plan.
> _______________________________________________
> USRP-users mailing list
> USRP-users at lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20150713/edf241c2/attachment-0002.html>

More information about the USRP-users mailing list