"Nikolai Vladychevski" <[EMAIL PROTECTED]> writes:
> Nikolai Vladychevski writes:
>
> > Ronald G Minnich writes:
> >
> >> On Fri, 24 Aug 2001, Nikolai Vladychevski wrote:
> >>
> >>> I think the way we should do it is incorporate code to kernel that
> >>> accesses
> >>> the DoC via MTD drivers (that are compiled into) and decompresses the
> >>> ramdisk image that resides just after the kernel on DoC into Ram and
> >>> mount
> >>> it as root ....
> >>
> >> we do this several ways. One is to mount an MTD partition as /, the other
> >> is to have Eric's elfboot stuff load the ramdisk and kernel into ram and
> >> then have the kernel mount the ramdisk.
> >>
> >>
> >> I have not tried using the mtd block device to get at the compressed
> >> ramdisk image. This should be easy.
> >
> > yes, the kernel has everything you need to do this..... but if you use
> > Eric's elfboot stuff, how much space you wold lose of the DoC's 8 MB?
> >
>
>
> I just seen the redhat's initrd uses 285K Bytes of code .....I hope using
> mtdblock would avoid losing this gold priced space.....
A clarification here. With mtdblock you should be able to say something like:
root=/dev/mtd0. And not need a ramdisk. I believe that is standard practice
when using the DOC Millenium.
So this is a seperate question from the ramdisk one.
Eric
