I've been poking around the xfree86 server side of dri a bit ... eg: hw/xfree86/drivers/ati/radeon_dri.c
and it occurs to me... why is this stuff in the core server? Why isnt it in the dri "module", rather than hacked into the main server? I've scanned through most of it, and it all looks like stuff that can be done in a module. (stuff that Utah-GLX, for example, does as a pure xfree86 module) Okay, so maybe one or two routines make use of the radeon register include files, hardware defs, etc. But so what? That stuff doesnt change much. Wouldnt it be much, much cleaner design to pull all that stuff out into the actual "module", rather than having to hack up the xfree86 server build process and decide ahead of time, "Am I going to build the server with DRI support or not?" ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
