* IXP4XX 64MB
[not found] ` <20090518170110.GI7042@n2100.arm.linux.org.uk>
@ 2009-11-15 21:18 ` Krzysztof Halasa
0 siblings, 0 replies; only message in thread
From: Krzysztof Halasa @ 2009-11-15 21:18 UTC (permalink / raw)
To: linux-arm-kernel
[a copy, I sent the follow-up mail to the old list address]
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
>> That was the solution. Now the main question is... why maintaining an
>> specific IXP4XX-Flash resource and driver when the general one works
>> so fine????
>
> A very good and fine question. There appears to be some explaination
> in drivers/mtd/maps/ixp4xx.c. I can't comment on its relevence though.
I checked this one (MTD_PHYSMAP on IXP4xx). It works in CPU big-endian
mode. It doesn't work in little-endian mode. Flash cmd/query data
swapping doesn't make it work.
I'll look at it but not at the moment.
Miguel, you're using it in BE mode only, aren't you?
--
Krzysztof Halasa
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-11-15 21:18 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <b0438a630905050354r51cce79dua6bfa669bff9ac2d@mail.gmail.com>
[not found] ` <b0438a630905180838o53881f7eg3dca7c68be6870c6@mail.gmail.com>
[not found] ` <20090518154453.GC7042@n2100.arm.linux.org.uk>
[not found] ` <b0438a630905180908y250fe950rd09fc1e5f5b0184@mail.gmail.com>
[not found] ` <20090518162610.GE7042@n2100.arm.linux.org.uk>
[not found] ` <b0438a630905180959w23bf6b0au1e147ba4471fafeb@mail.gmail.com>
[not found] ` <20090518170110.GI7042@n2100.arm.linux.org.uk>
2009-11-15 21:18 ` IXP4XX 64MB Krzysztof Halasa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox