Dave Airlie <[email protected]> writes: > However this means that pDrawable->pScreen will be a protocol > screen and the drivers will want to access the GPU screen.
Hrm. Sure would be nice if the drawables visible to the driver were also GPU objects? > So I'm left with two ideas on how to fix this (one ugly, one tedious): > a) introduce pDrawable->pCurrentGPU which is a screen ptr for the > currently rendering gpu on the drawable, the driver then uses this to > get its current screenptr back, instead of using pDrawable->pScreen. Could pScreen be the GPU object and we fix the rest of the server to use pProtocolScreen instead? Would that be easier to transition in the future to GPU-specific drawables objects (or, ideally, only pixmaps)? > b) add pScreen to all the driver facing APIs, (GCOps, Picture ops, > lots of ScreenRec). Yuck. -- [email protected]
pgpflA5zfWDN3.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
