alex at cendio.se
Wed Mar 8 05:21:41 EST 2000
On Wed, 8 Mar 2000, David Woodhouse wrote:
> alex at cendio.se said:
> > .
> > This is mainly used as a bootsector type of thing. The idea seems to
> > be that if your boot-code is a lot less than 64k you don't waste so
> > much space. And you can also store configuration data in one of the
> > smaller sectors, and rewrite it without destroying the boot sector.
> Options include...
> 1. Ignore the smaller erasesize - pretend it's 64Kb and force you to erase the
> whole lot at once.
> 2. Treat the parts with different erasesize as different logical devices as
> far as the MTD layer is concerned.
> 3. Change the MTD interface so it can handle variable sector sizes somehow.
> As you seem to be implying that the parts with different sector sizes are used
> for a different purpose than the majority of the flash device, I'm inclined
> to favour #2 for now.
Yes, i agree. Sometimes #1 might be a good idea too, it really depends on
how the flash is used. But we basically ignore this issue and let the user
make sure that their MTD devices look like constant size sectors.
To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org
More information about the linux-mtd