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

On Fri, Mar 21, 2008 at 12:35:39PM +0100, Segher Boessenkool wrote:
>>>> Convention is to use the stock ticker symbol.  If the company is
>>>> private and has no stock ticker symbol, then the company name should
>>>> be used.
>>>
>>> I didn't know that. ADI it is then.
>>
>> 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.

>> Stock ticker is a good choice for new things, but for anything from a
>> vendor which has existing 1275 bindings for its products, I think we
>> should keep the original assigned OUI, even if it differs from the
>> stock ticker.
>
> Yes, when there is an existing binding, obviously you should use what
> it says (unless that binding is *completely* broken).  Compatibility
> is good.
>
> 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.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2008-03-25 22:12 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 [this message]
2008-03-26 15:32                 ` Segher Boessenkool
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=20080325221209.GB8281@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=segher@kernel.crashing.org \
    --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).