[PATCH] powerpc: Create "rom" (MTD) device prpmc2800

Segher Boessenkool segher at kernel.crashing.org
Mon Jun 4 03:36:38 EST 2007


>> If it's a flash, compatible should be the chip type, and maybe as a
>> second entry, what type of flash protocol (amd, intel, cfi, ...) it's
>> compatible.
>
>     As I've already (and repatedly) stated before,

And you repeatedly got answers too, yet you choose
to rehash this whole discussion again.

> this gets you *nothing* WRT
> selecting the proper driver in the current Linux MTD subsystem.

Which Linux driver to use is not something that should
be (directly) communicated in a device tree -- even if
you take the position the device tree is a nice big
configuration file for Linux, what if a new Linux flash
subsystem shows up (or even simply a driver got renamed,
etc.) -- the device tree on your board doesn't necessarily
change when your kernel version does.

> What it
> actually *needs* to know is flash mapping information,

It needs to know what kind of flash it is, and how it
is connected -- i.e., it needs to describe the hardware.
How Linux then decides to use it is its own game, but
at least the device tree puts all the information it
could possibly need out there.

> the CFI/JEDEC interface
> then can be deduced by probing

Most of the time, sure.  Not always.

> -- so, this property ("ptobe-type"), although 
> specified in Documentation/powerpc/booting-without-of.txt, is optional.

Who is talking about "probe-type"?  We are talking
about "compatible".


Segher




More information about the Linuxppc-dev mailing list