mkfs.jffs2 propsal and a question about burst reads

Joakim Tjernlund joakim.tjernlund at
Tue Nov 6 08:45:11 EST 2001

> joakim.tjernlund at said:
> >    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. 
> Then JFFS2 would just have to erase the blocks in question anyway. Better 
> to just fix your bootloader or whatever you use to program the image in the 
> first place so that it erases any sectors which need it, and puts a clean 
> marker in them.

hmm, I don't follow you here. I don't mind that much that the blocks are erased
again by JFFS2, since it will(should) be a background job, but I would like
like to be able to tell JFFS2 whatever is after the initial image should be
considered non valid JFFS2 data and be put on the "to be erased" queue. 

> >    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. 
> You need chipset magic to do that.

I have the chipset magic(I think). I am using a MPC860 that has 
User Programmable Machine's(UPM). I am using one UPM to control my SDRAM
and the other UPM could be used to control the Flash. 

> --
> dwmw2

More information about the linux-mtd mailing list