Re: Dual core Power Mac G5

[Michael <macallan%netbsd.org@localhost>]

Hello,

On Nov 11, 2008, at 6:01 PM, Yevgeny Binder wrote:

> On Nov 11, 2008, at 9:57 AM, Michael wrote:
>
> > ...
> > I kinda-sorta succeeded getting my G5 booted over the network  
> > ( hint: the firmware wants your DHCP server to have the  
> > 'authoritative' flag set and you can feed it the kernel directly,  
> > without ofwboot.xcf ) but the kernel dies very early in the  
> > process. The early rasops console appears to work though, I got a  
> > few lines of output with wrong colours ( meaning it wasn't  
> > OF_write() ). Didn't make it to CPU attachment though.
> > I've been busy getting native Xorg going on all kinds of different  
> > hardware, hopefully I'll have time for the G5 very soon. Of course,  
> > any help is more than welcome.
>
> I've been out of the loop for a while since my Google SoC project,  
> so I don't know how relevant this is, but I did manage to netboot a  
> dual-processor single-core G5 into single user mode under its own  
> console after modifying Sanjay Lal's original code; I also had a  
> friend successfully boot a dual-core Power Mac G5 with the same  
> kernel. The patches (though now two years old) are available at http://netbsd-soc.cvs.sourceforge.net/viewvc/netbsd-soc/ppcg5 
> . I doubt that this code has been integrated into the official  
> sources, so it might be of some use to you now.

I've read through these sources for a bit and found a few things that  
may need attention
- why do you map 0x3fc00000 to VA 0xff800000? If OF needs it then  
there should be an entry for it in the translations property. Somehow  
I doubt it would be the same PA on my G5 ( with 2GB RAM, your address  
is 1GB minus 0x40000 )
- you hacked ofb to explicitly map the fb uncached. This is  
problematic for several reasons - first, ofb is deprecated and  
replaced with the MI genfb driver. Second, anything in PCI space  
should be mapped uncached by default to mimic the behaviour of older  
Macs, that's pretty much everything between 0x80000000 and the  
beginning of the firmware ROM ( 0xff800000 on my G5 ).

have fun
Michael