----- Original Message -----
From: Andreas Färber andreas.faerber@web.de To: The OpenBIOS Mailinglist openbios@openbios.org Cc: Sent: Monday, May 23, 2011 4:14 PM Subject: Re: [OpenBIOS] Getting Closer With Booting AIX? I Would Like to Help Please.
Am 23.05.2011 um 20:08 schrieb Kenneth Salerno:
can someone please look into this change I always have to make to get OpenBIOS ppc64 to compile? :)
--- arch/ppc/qemu/methods.c.ORIG 2011-05-23 14:00:23.832161400 -0400 +++ arch/ppc/qemu/methods.c 2011-05-23 14:00:36.769661400 -0400 @@ -38,7 +38,7 @@ rtas_instantiate( void ) { ucell physbase = POP(); - ucell s=0x1000, size = (ucell)of_rtas_end - (ucell)of_rtas_start; + ucell s=0x1000, size = (ducell)of_rtas_end - (ducell)of_rtas_start; unsigned long virt;
while( s < size )
First mention thereof, no error here.
Anyway, the real fix will be to change the cell size on ppc64 to 64-bit and to revert any workarounds for 32-bit ucell I applied before. That way, the size of ucell will be large enough for ptrdiff_t, too.
Now that I have QEMU working again for debugging, I'll focus on the cell issue the next days.
If you feel tempted to investigate the magic 260 further that would be appreciated. You posted logs of -m 1024, does it work with -m 259 and break with -m 260? Or is it different numbers on your host?
Cheers, Andreas
--OpenBIOS http://openbios.org/ Mailinglist: http://lists.openbios.org/mailman/listinfo Free your System - May the Forth be with you
Andreas, here is the behavior I'm seeing: if I set the memory allocation to 259M, I get this fatal error just as it finishes reading cd:,\ppc\bootinfo.txt:
OFMEM: ofmem_claim 0000412c 00000040 00000000 OFMEM: ofmem_map_page_range 00004000 -> 0000000000004000 00001000 mode 00000002 OFMEM: ofmem_claim 0000416c 00ecc600 00000000 OFMEM: ofmem_map_page_range 00004000 -> 0000000000004000 00ecd000 mode 00000002 OFMEM: ofmem_claim 0fe00000 00200000 00000000 OFMEM: **** ofmem_claim failure ***!
This is the moment where it would normally print "Welcome to AIX."
But, if I set the memory to 260, it gets further along, as you stated, however it eventually hangs with the NIP (Next Instruction Pointer register) just flapping between addresses 00000000fff91ac4 and 00000000fff91ad4
Regards,
Ken