thomas riddle <Tom.Riddle at Sun.COM> wrote:
> Suggestion of using inetboot was expected to provide issues as
> tracibility is difficult and UFSboot was thought to be an easier route.
>
> Since we have OF implementation on ODW and the capabilities of the
> Genesi team to enhance it, the choices came down to
> -------
> Use a TFTP boot to load a simplified PPC flavored multiboot and the
> boot_archive.
> * this is the most straighforward approach and least code intensive,
> small changes to current multiboot to remove BIOS calls. Not the best
> longterm solution.
Yesterday, I did talk with the person who did make the last changes
to ufsboot.
ufsboot includes a semi complete ELF interpreter and knows that krtld
is the load-interpreter for /platform/*/kernel/unix (see elfdump
/platform/*/kernel/unix).
ufsboot then loads krtld and krtld loads again /platform/*/kernel/unix
and then the files from the NEEDED tags.
If (what I expect) multiboot on x86 does the same, it would be a relatively
simple task to hack multiboot to match the PPC needs in case the ELF code
if already OK for PPC.
the OBP then would only need to load/execute the modified multiboot program and
to load the boot archive.
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
