[PATCH 4/9] [POWERPC] mv64x60: Fix FDT compatible names: mv64x60 => mv64360

Segher Boessenkool segher at kernel.crashing.org
Mon Mar 31 06:20:40 EST 2008


>> 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.




More information about the Linuxppc-dev mailing list