On Fri, Jan 25, 2002 at 09:41:52PM -0800, Philip Brown wrote: | > | > Probably I misunderstood your original comment. But just as a | > clarification, libGL doesn't provide an additional interface abstraction | > for OpenGL commands; it does some things for dispatch setup, and | > thereafter OpenGL calls from the application jump into the driver, | > preserving the OpenGL interface pretty much completely [...] | | When I say driver, I mean *driver*. | As in "a thing that gets loaded into the *kernel*"
I understand the source of the confusion now. But it would be good to get accustomed to the use of the term "driver" for software that drives a device, whether that software resides in the kernel or in userland. "Driver" is used for several pieces of software in the XFree86/DRI implementation, as you've noticed, but it's also used similarly in other systems. For example, the device-dependent OpenGL code on Windows is known as an ICD - Installable Client-side Driver. In Windows NT and descendants there is also a server-side driver running in a privileged mode, much as the DRM does in Linux. Allen _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
