From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: 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 00:58:53 +0200 [thread overview]
Message-ID: <200807170058.53599.arnd@arndb.de> (raw)
In-Reply-To: <20080716154646.GH24045@secretlab.ca>
On Wednesday 16 July 2008, Grant Likely wrote:
>=20
> > 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?
>=20
> This is bad for the same reason that "amcc,44x-<blah>" compatible values
> are bad in device nodes. =A0The definition of '*-44x-*' changes over 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.
=46or classic SOCs like 4xx or 52xx, the SOC familiy more or less defines
the platform, and all the details about peripherals can be expressed
in the device tree elsewhere.
If one board is so different that you need a separate board setup
in the kernel, it should simply not claim compatibility with the
SOC platform.
Arnd <><
next prev parent reply other threads:[~2008-07-16 22:58 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 [this message]
2008-07-17 2:15 ` Josh Boyer
2008-07-17 3:24 ` Segher Boessenkool
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=200807170058.53599.arnd@arndb.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.