-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jakob Bornecrantz wrote: > On 12 jan 2010, at 16.16, Chia-I Wu wrote: >> On Tue, Jan 12, 2010 at 10:52 PM, Jakob Bornecrantz >> <ja...@vmware.com> wrote: >>>> * Non-working >>>> * src/egl/drivers/dri/ >>> Having the dri driver working would be desirable since it allows >>> you to use >>> none gallium drivers standalone. >> The only problem with the dri driver is that no one is maintaining >> it. I agree >> that there might still interests in loading DRI drivers from EGL >> drivers. I >> wrote one for Android. >> >> How about we keep the xdri driver and leave dri driver in the git >> history? The >> xdri driver >> >> * dlopen()s DRI1/DRI2 drivers >> * talks with the X server using DRI1/DRI2 (the protocol) to implement >> functions like getBuffersWithFormat >> * works well >> >> The first point is the key idea shared by both dri and xdri drivers. > > The xdri driver is pretty much deprecated by the glx driver as it does > pretty much the same thing. The dri is more interesting then the xdri > driver since it is standalone from X.
Not entirely true. There is quite a movement within Khronos to get platforms off the platform-specific window system bindings and onto EGL. I support this plan as it provides a lot of benefit to Linux / X. * Windows applications written to EGL instead of WGL are just a little bit easier to port to a version of Linux that supports EGL on X. * Linux applications written to EGL instead of GLX are just a little bit easier to port to a version of Linux that doesn't use X. * iPhone / Palm Pre / misc. hand-held OS applications written to EGL are just a little bit easier to port to a version of Linux that supports EGL on X. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktOEuwACgkQX1gOwKyEAw9BAACgn1qqN8JolfHrBmWjVg5egS1P zzAAn3btB5FKivfvrkv1sBKAgJ7kFOhI =S2Jt -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
