Adam Jackson <[email protected]> writes: > Mesa doesn't ship DRI1 drivers as of 8.0, which is about 18 months and > three releases ago. The main reason to have wanted DRI1 AIGLX was to > get a GLX compositor working, but DRI1's (lack of) memory management API > meant that the cost of a GLX compositor was breaking direct GLX apps, > which isn't a great tradeoff. > > Of the DRI1 drivers Mesa has dropped, I believe only mga stands to lose > some functionality here, since it and only it has support for > NV_texture_rectangle. Since that's required for every extant GLX > compositor I know of, I conclude that anybody with a savage, say, would > probably not notice AIGLX going away, since they wouldn't be running a > GLX compositor in the first place. > > In the future we'd like to use GL in the server in a more natural way, > as just another EGL client, including in the GLX implementation itself. > Since there's no EGL implemented for DRI1 drivers, this would already > doom AIGLX on DRI1 (short of entirely forking the GLX implementation, > which I'm not enthusiastic about).
I think you also want to drop the DRI1 checks for AIGLX and AIGLX_DRI_LOADER in configure.ac. If you do: Reviewed-by: Eric Anholt <[email protected]>
pgpf4oeYaVwvG.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
