Bump protocol version to 1.4.
Bump package version to 2.7.
This new protocol request effectively allows clients to perform feature
detection on the DDX.
If I had DRI2GetParam in June 2011, when I was implementing support in the
Intel DDX and Mesa for new hardware that required a new DRI2 attachme
On 05/14/12 03:23 PM, Chad Versace wrote:
> + Parameter names in which the value of the most signficant byte is 0 are
> + reserved for the X server. Names in which the byte's value is 1 are
> + reserved for the DDX. Names in which the byte's value is neither 0
> + nor 1 are reserver
Tomorrow (Wednesday) I will submit a v3 of this series that addresses
your questions and suggestions. Comments below.
On 05/14/2012 05:51 PM, Alan Coopersmith wrote:
> On 05/14/12 03:23 PM, Chad Versace wrote:
>> +Parameter names in which the value of the most signficant byte is 0 are
>> +
On 05/15/12 05:19 PM, Chad Versace wrote:
>> Where will the master list of these be maintained to avoid conflicts?
>> Server
>> ones in dri2proto.txt/dri2proto.h and driver ones in each driver's headers?
> That is the plan; sorry for not documenting that. I will explicitly
> document that in dri
