Re: How can I prevent MTD to access the end of a flash device ?

[Josh Boyer]

On 11/22/05, Franck <vagabon.xyz@xxxxxxxxx> wrote:
> Hi,
>
> I have two questions that I can't answer by my own. I tried to look at
> FAQ and documentation on MTD website but found no answer.
>
> First question is about size of flash. I have a Intel strataflash
> whose size is 32MB but because of a buggy platform hardware I can't
> access to the last 64KB of the flash. How can I make MTD module aware
> of this new size. The restricted map size is initialized by my driver
> but it doesn't seem to be used by MTD.

The chip driver will detect a 32MiB chip from the CFI probe.  The map
size isn't really used by the chip driver, it's just needed to ensure
that the area is accessible.  What you could try doing is adding a
cfi_fixup function that changes the CFI data read in to remove the
last 64KiB of the chip...  not sure if that will work though.

> The second question is about the "cacheable" mapping field in map_info
> structure. I looked at others drivers and this field seems to be
> optional. Does this field, if set, improve flash access a lot ? Should
> I set up a cacheable mapping ?

Usually this isn't something you want to do especially with flash.  If
a cache line is flushed back to the chip it's probably not going to
work.  The cacheable mappings work for RAM based devices though.

josh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/