If you've got a system that has a pfour framebuffer, and would like to 
test out a NetBSD kernel that tries to deal with them, please let me 
know via private e-mail.

I remember someone saying to me once that OpenBSD's pfour code lost with 
a bwtwo, and I think I know why, and have fixed it in my version of pfour 
support.

BTW, the pfour stuff I have doesn't create a "pfour" bus (which was a 
hack, IMO, since it didn't represent what was really happening there).  
Instead, it treats pfour framebuffers as obio devices (like SunOS did) 
and uses the same PAs as SunOS kernel configurations (0xfb000000 for cgsix, 
and 0xfb300000 for bwtwo and cgfour).

Also, this pfour code is integrated directly into the generic framebuffer 
handling code ... no "special" routines for setting the size or resetting 
the device are necessary.

Anyhow, since I saw some discussion about it here recently, I thought I'd 
try to help out and hack on this ...

Ciao.

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939