A few questions (cramfs as root, flash permissions and JFFS2 on 2.2.18)

[Chris AtLee]

> My second question has to do with protection on the flash chip itself. 
> Whenever I try to mount a jffs image I get lots of errors saying that
> Erasing failed horribly.  So I tried the erase and eraseall utilities
> and get the message that I'm trying to erase a Read-Only filesystem.  My
> bootloader allows me to peek and poke memory manually, so I played
> around with locking / unlocking sections of flash and it seems that I
> can lock and unlock blocks of flash just fine, it's just that they
> aren't reported correctly by the Read Configuration command...Is this
> what is meant by "Legacy lock/unlock" in the MTD debug output?  MTD
> detects this at unsupported on my unit.

Ok, I fixed this problem by adding a command to mtd->unlock for the
addresses corresponding to the partition I want to be read/write.  Is
this the correct solution?

Cheers,
Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
Url : http://lists.infradead.org/pipermail/linux-mtd/attachments/20020503/a9feb3a1/attachment.bin