linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: DTS question
Date: Wed, 26 Mar 2008 16:32:28 +0100	[thread overview]
Message-ID: <f789af657dc6001f6337218db90825c5@kernel.crashing.org> (raw)
In-Reply-To: <20080325221209.GB8281@localhost.localdomain>

>>> Well.. stock ticker is the new convention.  IEEE1275 used IEEE
>>> assigned OUI strings (Organization Unique Identifiers).  Often those
>>> are the same as the stock ticker, but not always.
>>
>> Erm, an OUI is a 24-bit number.  I think you're confusing something
>> here.
>
> Yes, I think I am.  I somehow had the impression that in addition to
> the 24-bit OUIs used in MAC addresses, there were also string-form
> OUIs assigned.

Perhaps, I'm not an expert on this organisational stuff (wow, big
understatement).  OF uses only the six-hex-digit form though (with
a prepended 0, to make it unique).

>> Note that a stock symbol needs to be written in uppercase; in 
>> lowercase,
>> it is just a random name that has no collision protection.
>
> Um.. bit too late for that.  AFAIK, uppercase has been used by
> *no-one* for stock ticker derived vendor IDs.

No, it's used quite a lot actually.  Not in DTS files though ;-)

It doesn't matter a lot, lowercase names are perfectly valid, you just
don't get the nice non-collision reassurance you would get if you used
a name in one of the namespaces reserved for that purpose.

It's probably best to not use an uppercase stock symbol if you don't
have approval from the company in question anyway -- we use a
lowercase name (i.e. in the "free-for-all" space) for our messed up
bindings, the companies use an uppercase name (in the stock-ticker
namespace) for their own, incompatible, messed-up bindings, and
everyone is happy.  Or something like that.


Segher

  reply	other threads:[~2008-03-26 15:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 21:33 DTS question Sean MacLennan
2008-03-20 21:47 ` Segher Boessenkool
2008-03-20 21:48 ` Scott Wood
2008-03-20 22:19 ` Sean MacLennan
2008-03-20 22:26   ` Scott Wood
2008-03-21  4:12     ` Sean MacLennan
2008-03-21  4:34       ` Grant Likely
2008-03-21  5:09         ` Sean MacLennan
2008-03-21  7:05           ` David Gibson
2008-03-21 11:35             ` Segher Boessenkool
2008-03-25 22:12               ` David Gibson
2008-03-26 15:32                 ` Segher Boessenkool [this message]
2008-03-26 23:40                   ` David Gibson
2008-03-27  3:42                     ` Sean MacLennan
2008-03-21 11:31         ` Segher Boessenkool
  -- strict thread matches above, loose matches on Subject: below --
2008-09-02 21:56 Gary Thomas
2008-09-02 23:42 ` David Gibson
2008-09-03  0:14   ` Gary Thomas
2008-09-03  0:25     ` David Gibson
2008-09-02 23:43 ` Scott Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f789af657dc6001f6337218db90825c5@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=smaclennan@pikatech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).