On Mon, Mar 08, 2004 at 06:21:50PM -0800, James Bilotto wrote:
> On Mon, Mar 08, 2004 at 08:01:24PM +0100, Riccardo wrote:
> > James Bilotto wrote:
> > 
> > > can you post the log from the Xserver?
> > 
> > 
> > I attach it compressed.
> >
> > Fatal server error:
> > xf86MapVidMem: could not mmap screen [s=10000,a=a0000] (Invalid argument)
> 
> bummer, i was hoping it was something simple. i think that it can't mmap
> the frame buffer, don't know why. a friend of mine was working on
> something simuler for mac68k and other ports, i will ask him about it.
> untill then you can try the Xmacppc frame buffer server, it should work,
> but i can't remember where to get it from atm.

Sorry James, different issue...

The vgahw module for XFree86 is rather i386 specific and expects to find
the VGA memory window at 0xA0000.  OpenFirmware remaps this to a different
location.  Someone needs to teach the vgahw module to find the remapped
address.  This is needed for a number of cards including tdfx.

Being optimistic, I hope that this is the only issue keeping these drivers
from working.  I recall that OpenFirmware doesn't remap addresses below
0xFFFF which is where the VGA control registers live.

If I spent some time learning how to query remappings like this from
userland, I may be able to get this to work.  It doesn't seem that
/dev/openfirm has a man page.

It looks like I can use the ioctl()'s in dev/ofw/openfirmio.h to querry
the attributes/properties of a device node, but how is this info returned?
The ioctl() code in sys/dev/ofw/openfirmio.c seems to imply that they are
human readable strings.  Will this return the same junk that I see when
doing .properties under the OpenFirmware console?

-- 
   David P. Reese, Jr.                                  daver at gomerbud.com