On 11/05/2011 05:10 PM, Daniel Vetter wrote:
On Fri, Nov 04, 2011 at 11:30:06PM +0100, Thomas Hellstrom wrote:
I'm not sure whether / how you handle the case of hardware render to cursor surfaces on i915, but it seems to me like if a lot of drivers need to implement driver specific "tricks" to meet the semantics of a generic interface, we should perhaps consider specifying those semantics in a way that helps avoid driver-specific workarounds?
We don't handle really hanlde rendering to cursor objects. I think the "require a set_cursor after every cursor bo change" semantic is good, I've just feared that when only vmgfx needs this, no generic kms user will actually implement it. But nouveau seems to require this too, so I think at least for this case reality (and generic kms clients) will play along. -Daniel
Great. I'll cook up a header file patch with some extra documentation.
/Thomas