Hi,
Sorry that I don't have a better understanding of how DRI works. Maybe my idea is completely stupid, but I will try anyway:
I wonder, why the DRI-module linked into XFree depends on the hardware used. Wouldn't it be possible to make only the kernel-module being hardware specific?
My idea is that there is just one module for all graphics cards that goes into the XFree. At initialization time it asks the kernel, which functions are supported by the hardware. Then it uses a common API to talk to the kernel-module and non-existing functionality is overriden by the software-mesa.
Well, I guess that if this was possible it had already been implemented, so why is this idea not good?
Anything's possible.
This way of doing things would necessarily transfer a large amount of userspace code to the kernel, which is considered a bad idea by most people.
There'd also be the issue of how applications could talk to that code, but the above is pretty much the killer: The code doesn't have to be in the kernel, there is no huge user-visible advantage to having it there, so it shouldn't be there.
Keith
------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
