Re: [OpenBIOS] [Qemu-devel] Re: QEMU OpenBIOS booting?

[Blue Swirl]

On 4/20/09, Laurent Vivier  wrote:
> Le lundi 20 avril 2009 à 11:39 +0200, Laurent Vivier a écrit :
> > > In message: 
> > >            Blue Swirl  writes:
> > > : On 4/19/09, M. Warner Losh  wrote:
> > > : > In message: 
> > > : >
> > > : >             Steven Noonan  writes:
> > > : >  : I eventually decided it made more
> > > : >  : sense to get QEMU working instead. I did notice that the pre-OpenBIOS
> > > : >  : version of QEMU was able to boot Mac OS X via Open Hack'Ware, so I was
> > > : >  : annoyed to find that OpenBIOS didn't have such support. So, I might as
> > > : >  : well add it.
> > > : >
> > > : >
> > > : > Open Hackware was barely enough to boot older versions of Linux.
> > > : >  Other operating systems that needed more extensive properties from the
> > > : >  OpenFirmware device tree failed to boot because they weren't present.
> > > : >  I was involved in a large effort to get FreeBSD/powerpc booting on
> > > : >  QEMU only to have it fail utterly because the amount of hacking on
> > > : >  OpenHackWare needed was rather large and mysterious...
> > > :
> > > : This is what I get with OpenBIOS:
> > > : >> *** Boot failure! No secondary bootloader specified ***
> > > :
> > > : 0 > boot cd:,\boot\loader cd:0
> > > : Consoles: Open Firmware console
> > > :
> > > : FreeBSD/Open Firmware/PowerPC bootstrap loader, Revision 0.1
> > > : ([e-mail], Thu Apr 16 18:47:58 UTC 2009)
> > > : Memory: 131072KB
> > > : Booted from: cd
> > > :
> > > : Loading /boot/defaults/loader.conf
> > > : /boot/kernel/kernel data=0x4a4ce0+0x3d4e4 syms=[0x4+0x454f0+0x4+0x5a4b9]
> > > : /
> > > : Hit [Enter] to boot immediately, or any other key for command prompt.
> > > : Booting [/boot/kernel/kernel]...
> > > : Kernel entry at 0x13dac0 ...
> > > : panic: moea_bootstrap: no space to copy translations
> > > : Uptime: 1s
> > >
> > > That's similar to the one that I've seen as well.  The problem with
> > > this one, IIRC, is that FreeBSD/powerpc is trying to setup the memory
> > > translations for the MMU and the 'translations' property length is
> > > zero, or something like that...
> >
> > It seems there is the same problem with the Haiku bootloader, I have a patch to correct this.
>
> Could you try the attached patch, please ?

No change.