On Die, 2003-03-25 at 21:37, Ian Romanick wrote: > > In the current GLX visual mechanism, the DDX driver exports an array of > __GLXvisualConfigRec objects that is used by the GLX extension. This is > done because the DDX driver is the only place in the server that knows > what display modes the hardware can support. There are two significant > problems with this, but only the first was initially apparent to me. > > There is no easy way for the DDX driver to export the extended visual > information needed for fbconfigs to the GLX layer. The primary issue is > binary compatability. The size of the __GLXvisualConfigRec structure > cannot be changed, and I have not been able to find a way to communicate > version information between the GLX layer and the DDX driver.
Maybe I'm missing something, but one could always play tricks like add a symbol to the GLX module and check its presence from the DDX driver? [ GLX layer loading the DRI driver ] > This could also pave the way for the X server to use the new memory > manager that is being developed. We could make some sort of a conduit > for the X server to call into the DRI driver to allocate graphics / AGP > memory. There are other ways to achieve this, but this would be an easy > way. I assume this is only about the user space layer of the memory manager, and the core will always be in the DRM? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
