... | @@ -18,6 +18,31 @@ driver: |
... | @@ -18,6 +18,31 @@ driver: |
|
https://www.ohwr.org/project/fine-delay-sw/tree/master
|
|
https://www.ohwr.org/project/fine-delay-sw/tree/master
|
|
and in the carriers, e.g.
|
|
and in the carriers, e.g.
|
|
[spec-sw:](https://www.ohwr.org/project/spec-sw/wikis), during the early
|
|
[spec-sw:](https://www.ohwr.org/project/spec-sw/wikis), during the early
|
|
bootup process:
|
|
bootup
|
|
|
|
process:
|
|
https://www.ohwr.org/project/spec-sw/tree/master
|
|
https://www.ohwr.org/project/spec-sw/tree/master
|
|
|
|
|
|
|
|
### Q: What is the origin of the vendor\_id and device\_id for the wishbone devices?
|
|
|
|
|
|
|
|
What is the origin of the vendor\_id and device\_id for the wishbone
|
|
|
|
devices that are connected to the wishbone crossbar (defined in the
|
|
|
|
SDB)?
|
|
|
|
I see that CERN chose vendor\_id "0000CE42". What number should I give
|
|
|
|
to our company? The device\_id seems a random number. Are these numbers
|
|
|
|
managed somewhere or could I freely choose some?
|
|
|
|
|
|
|
|
A: Nobody is mangaing these numbers. As long as we are just the few of
|
|
|
|
us, we agree on numbers. The standard says that the high-half is free
|
|
|
|
for anyone to use, provided the vendor is randomized. And for the device
|
|
|
|
number, it's a little local mess. finedelay is ascii-like 0xf19ede1a,
|
|
|
|
ADC is an md5 hash of the device name and others are sequential (the vic
|
|
|
|
is 0x13).
|
|
|
|
|
|
|
|
In general, each vendor is on its own. We'd better not have duplicates,
|
|
|
|
but it's not really that bad unless it's a top-level thing that is used
|
|
|
|
for higher-level identification.
|
|
|
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
8 July 2013
|
|
|
|
|