splitting drawable and screens

Keith Packard keithp at keithp.com
Fri Oct 5 09:53:23 PDT 2012


Dave Airlie <airlied at gmail.com> writes:

> I considered this, but really drawables are generally a protocol
> object, in a lot of cases a Window which really has no interesting
> properties to a GPU.

Yeah, getting to the point where the only GPU visible objects are
pixmaps would be great; that's the surface we're drawing to, after
all. It seems like making that migration within the current API might
actually be fairly straightforward? Hack up the Picture code so that all
coordinates are screen-relative and just start passing the window
pixmap, then do the same for GC rendering?

> So since ajax has convinced me for GCs and Pictures that I really want
> per-GPU versions, I was think of adding a pScreen to Picture and to a
> few interfaces like GetImage need changes, but much reduced.

Are you thinking that the existing GC and Picture structs become the GPU
versions and that we create new protocol structs then? Otherwise, we'll
run into a constant stream of confusion over which "kind" of struct each
API requires, right?

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20121005/8baa9f3c/attachment.pgp>


More information about the xorg-devel mailing list