mkfs.jffs2 propsal and a question about burst reads
joakim.tjernlund at lumentis.se
Tue Nov 6 06:40:18 EST 2001
Hi it's me again ..
with some more questions/suggestions
Before I can install a new JFFS2 FS image(produced with mkfs.jffs2) I have
to erase the whole flash partition, then copy the image(with cp image /dev/mtdlock4)
the device. Then I boot linux and now JFFS2 will re-erase all unused blocks.
If I skip the initial erase, then JFFS2 will be confused by the earlier
JFFS2 contens which remain after the previous JFFS2 FS that were on the flash.
I think this is the expected behavior, correct?
I find it unconvinient and time consuming to erase the WHOLE flash partiton
before I can install a new FS image. Therefore I wonder if it would
be possible to add some flag/end marker in JFFS2 that mkfs.jffs2 could
set, so that JFFS2 knows that the flash space after the maker does not
contain valid JFFS2 data. Once JFFS2 has recongnized its FS, JFFS2 would
delete the end marker and resume normal behaviour.
What do you think?
I am using Intel Strata Flash and this flash can do burst reads, so was
thinking that if I were to enable burst read I would gain performance.
I rember some discussion about this a while back, but I did not see
any positive reports about gained performance. Has anybody done
this and did you gain any performance?
More information about the linux-mtd