Backing out DRI2 from server 1.5

[Keith Packard]

On Sun, 2008-08-10 at 19:11 -0400, Kristian Høgsberg wrote:
> On Sun, Aug 10, 2008 at 5:07 PM, Dave Airlie <airlied at gmail.com> wrote:
> > On Mon, Aug 11, 2008 at 5:46 AM, Kristian Høgsberg <krh at bitplanet.net> wrote:
> >
> >> My plan is to included a device specific 32 bit bitfield per buffer in
> >> the reply to DRI2Getbuffers, which is what the client calls to ask the
> >> server for buffer info.  These bits can indicate properties such as
> >> tiling.  In the DRI2Connect call, I'm sending back the DDX version, so
> >> the DRI driver will know which bits are valid.
> >
> > I actually meant to cc the lists on this, I dislike device specific
> > limited allocation bitfields
> > as an API in general, can we add something with a pointer or length + array?

There are so many possibilities here. I'd rather see something that
didn't require a secret agreement between the server and client though.
That seems prone to versioning failures.

One answer would be to have a version number and then a random
collection of bytes; that at least would let us change the encoding in a
reasonably compatible fashion.

Another alternative is a sequence of name/value pairs, where each value
was a homogenous array of values.

A third alternative is to have driver-specific requests to return this
kind of data. That would let us completely document what was on the
wire, although it would consume one request ID for each driver.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20080810/df2bad37/attachment.pgp>