Thanks for the patch. I've thought about doing that, but it seemed to me it
was something so much important that it would already be in some official
Does it mean that NONE of the existing embedded linux is able to use a ROM
directly as a filesystem ?? (either root fs or not)
I'm astonished. Is there some embedded-specific mailing list I'm not aware of?
On Thursday 13 December 2001 17:22, Bradley D. LaRonde wrote:
> I have maintained, on and off, a patch to crafms that supports traditional
> cramfs decompress-and-read/run-from-RAM, plus direct mmaping with no
> decompression and read/run straight out of ROM:
> > I'm looking for a way to put a filesystem into ROM.
> > Seems pretty trivial, isn't it ?
> > My understanding is (the way initrd does, and the way I do as of today)
> > * create a RAMDISK
> > * loads the data into ramdisk
> > * mount the ramdisk
> > problem is that I don't want to waste the RAM as the data in the ROM is
> > already in the address space. (it's an embedded system, btw)
> > Speed is not an issue here. ROM access might be slower than RAM, it will
> > always be so much quicker than a disk access. (wrong?)
> > Ideally, i would give address/length of the fs in ROM to a function, and
> > I would get a ramdisk configured to read its data exactly there, and not
> > in ram.
> > Any hint ?
> > I've tried to look in the different options from mainstream kernels and
> > embedded-oriented kernels whithout success.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:26 EST