[PATCH] powerpc: Create "rom" (MTD) device prpmc2800
sshtylyov at ru.mvista.com
Mon Jun 4 22:41:54 EST 2007
Benjamin Herrenschmidt wrote:
>> No, it doesn't -- since that info is almost *absolutely* useless
>>exception is "cfi") in the context of Linux MTD subsys.
>> Please, try to understand that knowing that chip is CFI compatible in
>>itself doesn't yet guarantee that you can access the chip -- it all depends on
>>its mapping to the real physical address range, therefore this group IMO
>>cannot even constitute a valid "compatible" property.
> You make no sense to me. It's like saying that knowing that a 8250 chip
> on ISA cannot be accessed if you don't know it's IO ports so it
> shouldn't say "8250" in compatible property ?!?!?!?
No, it's a completely different case. Base address and even flash size
are not the only things that matter. There's bus width and interleave factors
that influence the access (and possibly, byte-swapping too, although this is
unlikely to happen in PPC world).
> Also, whatever shortcomings of the linux MTD drivers are totally
> irrelevant to what is correct to have in a device-tree. While we do
> tailor our device-tree specification around linux needs in most cases,
> there are cases like this one where common sense should be enough to
> understand that it's not because the linux MTD subsystem, as of today,
> cannot be told what programming interface to use, that we shouldn't
> provide that information in the tree.
We did provide it, in the form of probing hints ("probe-type" prop).
> Regarding physical address ranges for the flash mapping, I suppose the
> best is to define a property for flash chips for it.
Flash chips in themselves have little to do with how they are mapped to
the physical address space (considers the interleave factor), so that doesn't
seem a practical idea.
More information about the Linuxppc-dev