From: Segher Boessenkool <segher@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 4/9] [POWERPC] mv64x60: Fix FDT compatible names: mv64x60 => mv64360
Date: Sun, 30 Mar 2008 21:20:40 +0200 [thread overview]
Message-ID: <cca3a75a9de9aad936df234195f97bb7@kernel.crashing.org> (raw)
In-Reply-To: <20080329215753.GA27226@lixom.net>
>> Compatible names should refer to a specific version of the hardware,
>> without wildcards. Change each instance of mv64x60 to mv64360, which
>> is the oldest version we currently support.
>
> Actually, it's normal to have more than one compatible field, from
> specific to generic. So it should make sense to have both (with the
> 64360 entry first).
The normal use is to have the exact device first, and older devices
that the device is compatible to after that.
There is no such thing as a "generic" device, in general. It's a
mistake to define generic "compatible" values [*], that's like
trying to predict the future -- how can you guarantee that all
future devices in a device family will be compatible?
Segher
[*] In certain cases, like usb-ohci, there _is_ a defined interface
for all future devices. Also, "legacy" devices have a de facto such
interface.
next prev parent reply other threads:[~2008-03-30 19:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 23:39 [PATCH 0/9] powerpc: mv64x60 and prpmc2800 DTS cleanups Dale Farnsworth
2008-03-28 23:42 ` [PATCH 1/9] [POWERPC] mv64x60: change FDT compatible prefix to mrvl Dale Farnsworth
2008-03-28 23:47 ` Grant Likely
2008-03-29 0:00 ` Dale Farnsworth
2008-03-29 0:12 ` Grant Likely
2008-03-30 23:44 ` David Gibson
2008-03-31 16:56 ` Dale Farnsworth
2008-04-01 1:53 ` David Gibson
2008-03-28 23:44 ` [PATCH 2/9] [POWERPC] prpmc2800: convert DTS to v1 and add labels Dale Farnsworth
2008-03-28 23:45 ` [PATCH 3/9] [POWERPC] prpmc2800: fix frequencies in prpmc2800.dts Dale Farnsworth
2008-03-28 23:47 ` [PATCH 4/9] [POWERPC] mv64x60: Fix FDT compatible names: mv64x60 => mv64360 Dale Farnsworth
2008-03-29 21:57 ` Olof Johansson
2008-03-30 19:20 ` Segher Boessenkool [this message]
2008-03-31 16:33 ` Dale Farnsworth
2008-03-28 23:48 ` [PATCH 5/9] [POWERPC] mv64x60: remove device tree absolute path references Dale Farnsworth
2008-03-28 23:49 ` [PATCH 6/9] [POWERPC] prpmc2800: clean up dts properties Dale Farnsworth
2008-03-29 21:59 ` Olof Johansson
2008-03-30 10:11 ` David Gibson
2008-03-31 16:43 ` Dale Farnsworth
2008-04-01 1:17 ` Segher Boessenkool
2008-04-01 2:22 ` David Gibson
2008-03-28 23:50 ` [PATCH 7/9] [POWERPC] mv643xx_eth: prepare to support multiple silicon blocks Dale Farnsworth
2008-03-28 23:51 ` [PATCH 8/9] [POWERPC] Document the mv64x60 device tree bindings Dale Farnsworth
2008-03-28 23:52 ` [PATCH 9/9] [POWERPC] prpmc2800 needs a dtbImage Dale Farnsworth
2008-03-28 23:56 ` Grant Likely
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=cca3a75a9de9aad936df234195f97bb7@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
/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).