-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kristian Høgsberg wrote: > > That's the case I was describing in the last sentence. When the DDX > gets the set of buffers to allocate it doesn't know whether to > allocate 16 or 24 bit depth buffer. What I'm suggesting is that we > add a new buffer token to the DRI2 protocol, DRI2BufferDepth16, which > the dri driver can use to indicate that it wants a 16 bit depth buffer > even if the drawable is 24 bpp. It requires a dri2 proto bump, and > the loader needs to tell the dri driver that the DRI2BufferDepth16 > token is available.
Err....this is a bandaid on a bigger problem. What about 24-bit depth with 16-bit color? What about when we start to support multisampling? Etc. If the DDX needs the fbconfig information, why not just give it the fbconfig? Right? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknSdyEACgkQX1gOwKyEAw+9YwCfc44rwsm8kfapo/RSFL0KfhEd 68wAnjRK4Ng5bCpvqmnVHC0KqCWyOYll =4J9j -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
