* loading cramfs initrd at startup
@ 2008-09-19 17:51 Ben Dooks
0 siblings, 0 replies; only message in thread
From: Ben Dooks @ 2008-09-19 17:51 UTC (permalink / raw)
To: Linut MTD
I am looking at a customer who's system loads an cramfs initrd
from /dev/mtdblock1 (NAND) via a hack that makes mtdblock map
out bad blocks so that the initrd loader does not see errors
during the load.
I was wondering if anyone had any comments about a better way
to do this without patching up drivers/mtd/mtdblock.c?
My initial thoughts are:
1) Add a configuration option to make mtdblock remove any defects
from a specified parititon (fromalise the hack)
2) Add new block device, possibly named mtdcont which provides an
read-only interface and a similar function to mtdblock but
mapping out the defects.
3) Change the initrd loader to understand the block layout of the
system and skip bad blocks during loading.
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-09-19 17:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-19 17:51 loading cramfs initrd at startup Ben Dooks
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox