using the DOC2000

Russ Dill Russ.Dill at
Wed Jan 23 18:47:35 EST 2002

I've been using 2 MB of standard flash on an ARM system. The layout I've
been using is:

boot blocks
	32k - boot loader (blob)
	8k - journaled config
	8k - journaled config
	16k - static config
main blocks
	128k * 3 - backup cramfs
	128k * 12 - primary cramfs

both cramfs filesystems contain their own kernel, and the bootloader can
boot either. I'm trying to port this over to x86 using a DOC2000. I'm
trying to translate how I'm currently using MTD, to how I need to use a
DOC2000. the only writing that occurs to the flash is the initial flash
of everything, the periodic (every 4 hours to every few days) writing of
the journaled config blocks, and the updates to the primary fs (once
every few months). Currently as it stands, it seems for the DOC to be
usefull at all, I need to use NTFL, which I don't paticularly care for.
I'd like to mount my cramfs on a read only block device, as well as
control the writing of the journaled config, as well as their erase
blocks, so that I know what is going on with the flash in case power is

Does lilo need NTFL to be able to boot linux off of the device? does
grub? Can I control erase cycles for my journaled config if I am using
NTFL? What is all this talk about ECC?

More information about the linux-mtd mailing list