linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Victor Gallardo <vgallard@amcc.com>,
	fkan@amcc.com, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] Add AMCC Arches 460GT eval board support to platforms/44x
Date: Thu, 17 Jul 2008 05:24:29 +0200	[thread overview]
Message-ID: <259d93b7d6b03cada58fecaf875fea31@kernel.crashing.org> (raw)
In-Reply-To: <200807170058.53599.arnd@arndb.de>

>>> Shouldn't it be enough to have a common compatible value in each
>>> of these boards, e.g. "amcc,generic-ppc44x" and then just ignore the
>>> specific type unless you need to do something special?
>>
>> This is bad for the same reason that "amcc,44x-<blah>" compatible=20
>> values
>> are bad in device nodes. =A0The definition of '*-44x-*' changes over=20=

>> time as
>> new parts are added. =A0Compatible values should always reflect an =
exact
>> part number.
>
> I agree in general, but I also think that all 44x boards should be
> regarded as the same machine time, in the same way that all powermacs
> are detected as compatible with "Power Macintosh" or "MacRISC", or
> how all sorts of serial ports claim compatibility with i8250.

And they can do that because a binding for those "compatible" names
exists, that describes exactly what it means for a device to be "i8250"
or "MacRISC" (well, in that last case, maybe such a binding exists, or
maybe it doesn't, but we don't know about it anyway, sigh).


Segher

  parent reply	other threads:[~2008-07-17  3:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  5:33 [PATCH] Add AMCC Arches 460GT eval board support to platforms/44x fkan
2008-07-16 11:50 ` Josh Boyer
2008-07-16 14:15   ` Grant Likely
2008-07-16 14:37     ` Josh Boyer
2008-07-16 15:43       ` Grant Likely
2008-07-17  3:15       ` Segher Boessenkool
2008-07-16 14:46     ` Arnd Bergmann
2008-07-16 15:46       ` Grant Likely
2008-07-16 22:58         ` Arnd Bergmann
2008-07-17  2:15           ` Josh Boyer
2008-07-17  3:24           ` Segher Boessenkool [this message]
2008-07-17  3:19         ` Segher Boessenkool
2008-07-18 22:31   ` Victor Gallardo
2008-07-19 13:44     ` Josh Boyer
2008-07-22 19:35       ` Victor Gallardo
2008-07-18 14:24 ` Stefan Roese
2008-07-18 22:24   ` Victor Gallardo

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=259d93b7d6b03cada58fecaf875fea31@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=fkan@amcc.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=vgallard@amcc.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).