On 7/3/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> Why aren't the DRI drivers themselves EGL drivers? That's sort of the model I
> was anticipating:
>
> - eglChooseDisplayMESA("display/0")
> - EGL translates to /dev/dri/card0, opens it
> - ioctl: what's the DRI driver name for this device?
> - kernel: i915
> - EGL loads i915_dri.so, calls its egl setup
> - eglCreateContext notices the attached dri driver, does device setup
>
> I guess I don't see the point of loading one module to have it load another,
> particularly if that first module is always getting loaded.
Brian wants to keep libEGL crossplatform and generic so this forces me
into a third library. I'm putting all of the common code into the
third library too. It contains code similar to miniglx.c
--
Jon Smirl
[EMAIL PROTECTED]
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
