jffs2 with sync burst mode
lists at ku-gbr.de
Thu Mar 10 11:40:24 EST 2005
Am 2005-03-10 15:54 +0000 schrieb Artem B. Bityuckiy:
> OK, why does this mean JFFS2 is guilty of this? Why don't you suspect your
> drivers? Why don't you suspect that you flashed your (say, correct) image
The image is created in different ways, copied, dd'ed, mkfs.jffs2. Same
All other constellations in software on this Hardware are working
Kernel XIP out of this Flash device with this settings runs perfect.
No matter if partitions are cat'ed or dd'ed or files copied and such:
identical md5sums read back.
I tested cramfs as rootfilesystem which works ok also.
> Just configure your kernel properly: switch on the "Test driver using RAM"
> (MTD_MTDRAM) option in your kernel configuration. Type "modprobe mtdram"
> if you have configured it as the kernel module.
> If you do this your JFFS2 will work over emulated 4MiB in-RAM flash and
> this will help you to exclude driver problems.
No clue until now. On Host-PC or on the embedded system?
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
More information about the linux-mtd