jffs2 with sync burst mode
lists at ku-gbr.de
Thu Mar 10 12:02:23 EST 2005
Am 2005-03-10 16:21 +0000 schrieb Artem B. Bityuckiy:
> Looks like JFFS2 really reads messed data from flash and I think this
> isn't JFFS2'd failure.
So it reads wrong length of name (always too less)
and wrong data which always is one byte
located somewhere before the name itself in flash.
When Hardware is broken, why does it not read name lengths too long
sometimes or reads data which is not found in the image a couple of
bytes before the filename? Is this possible?
Well, may be... hence my question. But I have no clue anymore where to
search. I hacked onto this burst mode for weeks and only jffs2 is not
working in always a similair pattern.
Thats why I show up here, may be burst mode is broken for this system
and that only for jffs2. But I don't know how this filesystems works
exactly when reading and I am trying to find out which fucking bug in
hardware it could trigger, all other tests run fine.
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
More information about the linux-mtd