On Sat, 2004-07-17 at 13:47 -0700, Jon Smirl wrote: > > > On the other hand the fb_dri driver needs to know everything about the > framebuffer in order to work. But it can get this info by querying the > fbdev driver.
Shouldn't libGL shield the drivers from things like this? > Also, how does __driCreateNewScreen() work with RandR? If the mode is > changed the framebuffer parameters will change too. They don't in the XFree86 RandR implementation, which AFAIK is still basically unchanged in the X.Org tree. There are many other reasons the buffer parameters should be handled more dynamically though, the most pressing probably being the composite extension. I understand the sis drivers have always used per-drawable buffers. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
