Roland Scheidegger wrote:
2b) same as above, but tweak the client-side ddx version check to allow for ranges of ddx major versions instead of a single ddx major version (so new dri drivers can work with both old and new ddx, but new ddx will still require new dri driver).
2c) same as above, but only advertise bumped version if tiling is enabled in xorg.conf.
We may be able to avoid this particular class of problems in the future by doing "creative" things with fbconfigs. Basically what we have here is a case where all the fbconfigs supported by the server have an invisible (to the application / user) "tiled memory" flag. The old DRI drivers don't support any fbconfigs with "tiled memory". When the CallCreateNewScreen (src/glx/x11/glxext.c, line 727) calls filter_modes (same file, line 654) to determine the set of available fbconfigs, filter_modes will return 0. In that case, CallCreateNewScreen would just fail.
The only trick is getting that extra flag sent on the server-side. :(
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
