Sven Luther <sl at bplan-gmbh.de> wrote:
> On Wed, Jan 11, 2006 at 05:37:25PM +0100, Joerg Schilling wrote:
> > Sven Luther <sl at bplan-gmbh.de> wrote:
> >
> >
> > > Well, i am not sure if i am missing something, but i think the unix +
> > > boot_archive situation is not all that different from what i see in the
> > > linux
> > > world, where we have the kernel and a ramdisk, which contains a (minimal)
> > > root
> > > filesystem as well as a kernel modules.
> >
> > The boot environment need to load the ramdisk and the multiboot
> > program. multiboot loads unix.
>
> And unix is in the ramdisk, right ?
correct.
> So, basically, to experiment this, i need only access to the multiboot
> program, have this multiboot get the address of the ramdisk somehow, and put
> some bogus program in it, as well as some data. Maybe a program which will
> print its argument and the content of a file found in the ramdisk to the OF
> console or something such, and that would be enough to test the firmware
> needed functionality here ?
The multiboot program needs to know where the ramdisk is in memory.
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
