-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Keith Packard wrote:
> Yes, it should be backward compatible. The req is smaller than the rep, > so adding new members won't change the alignment. Also, as the flag > indicates whether the additional data is present, older clients won't > accidentally trigger the optimization. Furthermore, as this is purely an > optimization, newer clients needn't even bother to check for the kernel > version. We can bump the minor version, but I'm not going to add checks > for it. It is probably worth bumping the minor (or the driver date) just to make it easier to determine what the user has installed when / if bug reports come in. Debugging possible interactions between pre-optimization vs. post-optimization code paths will be difficult without. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVwYgX1gOwKyEAw8RAjASAJ9r3yBihE5ffb3ARlT2VX7UUw590gCbBeo9 h/S9lUmu3TTy9YrTwSimm/g= =0XDQ -----END PGP SIGNATURE----- ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
