On Tue, Jan 17, 2006 at 05:48:13PM +0200, Cyril Plisko wrote: > On 1/17/06, Joerg Schilling <schilling at fokus.fraunhofer.de> wrote: > > Cyril Plisko <cyril.plisko at gmail.com> wrote: > > > > > On 1/17/06, Joerg Schilling <schilling at fokus.fraunhofer.de> wrote: > > > > Cyril Plisko <cyril.plisko at gmail.com> wrote: > > > > > > > > > > BTW: did someone find out how multiboot gets the address of the > > > > > > loaded ramdisk? > > > > > > > > > > > > > > > > I think grub passes that info to multiboot. > > > > > > > > I thought this too, but I could not find the related data. > > > > > > Here it is: > > > http://www.gnu.org/software/grub/manual/multiboot/multiboot.html#Boot%20information%20format > > > > But what should be the pointer to the ramdisk? > > Do you believe that this is "load_addr"? > > mod_start as far as I can tell
We probably need both the ramdisk physical address (altough multiboot can maybe use the virtual address) and probably the ramdisk size also, if we want to allow for a compressed ramdisk image that multiboot could then uncompress in place. Friendly, Sven Luther
