Sprite transforms in RandR
keithp at keithp.com
Mon Dec 6 08:44:41 PST 2010
On Mon, 6 Dec 2010 15:20:01 +0000, Daniel Stone <daniel at fooishbar.org> wrote:
> Nope, we don't have any per-CRTC differences there, it's just that
> rotation is essentially another property of the mode that we need to know
> about in order to set up both the CRTC and the underlying surfaces,
> rather than an additional BlockHandler and a transform somewhere.
If we don't have any existing hardware which requires per-CRTC scanout
formats, I have to admit I'm tempted to leave the interface alone
instead of making things more complicated for both applications and the
> > This also required a patch to add a rotate hook to the RandR CRTC API
> which let the driver deal with rotation requests and skip the whole
> shadow + copy nightmare. I did have this on p.fd.o at one point, but it
> appears to have been lost; Tiago might know where it is.
I'm hoping the new 'set' entry point will do what you want; it gets
called before xf86CrtcRotate in every case now (unlike set_mode_major
which doesn't get used when the server changes only the origin).
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the xorg-devel