http://bugs.freedesktop.org/show_bug.cgi?id=6355





--- Comment #31 from George - <[EMAIL PROTECTED]>  2008-04-24 07:14:52 PST ---
(In reply to comment #28)
> I was thinking about making GLcore a DRI driver.  The DRI driver interface now
> has an extension mechanism that allows us to advertise alternative entry
> points, which I use for legacy DRI support now.  This mechanism could also be
> used to provide entry points that doesn't require drm or sareas or the like. 
> Then the DRI loader in the X server (and libGL even) could look for the sw
> renderer entry point and call that if the hw entry points fails or if the
> loader doesn't support them.
> 

I definitely agree with you that this is the right solution, but has not
happened for years. Granted the new dri interface makes this easier but the
work still remains to be done. With a little imagination __GLcoreModuleRec is
pretty close to  __DRIlegacyExtensionRec and can be massaged to the later
during the xserver 1.6 timeframe, unless you want to start a new.

I would be glad to see the above finally implemented and the __GLcoreModuleRec
ripped off.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to