On Mon, 14 Feb 2005 14:18:26 -0600, Ryan Underwood <[EMAIL PROTECTED]> wrote: > I've been looking at Xgl and mesa-solo recently and my interest has been > piqued. I have been hacking on the mga drivers for a while now. What > do we need to do to the mga framebuffer, DRM, DRI, and/or XAA drivers in > order for the whole mga stack to be ready for Xgl and/or mesa-solo? How > does the VGA/VESA console get along with this (i.e., is a framebuffer > console a prerequisite?) What about restoring a sane state in the case > of a software failure (either to the console or to the X server)?
Look at how mesa-solo and the radeon driver work together. Right now mesa-solo uses the radeon fbdev driver for mode setting. Dave Airlie can probably give you hints on how to test that everything is working right in an mga mesa-solo. No on has tried getting XGL running on top of mesa-solo. I don't know of any obvious reason why it shouldn't work other than no one has tried doing it yet. First check out that your mga mesa-solo is running, there are test programs in the mesa tree for this. Then try to get XGL running on top. This may require some work to XGL but post your issues to the [EMAIL PROTECTED] and [EMAIL PROTECTED] lists and someone will answer. There is code in the X server for frequency scaling on radeon chips. This is probably something that should be moved down into the radeon fbdev or DRM drivers. -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
