From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: KMS cursor BO semantics
Date: Sat, 5 Nov 2011 17:10:34 +0100 [thread overview]
Message-ID: <20111105161034.GA2942@phenom.ffwll.local> (raw)
In-Reply-To: <4EB4676E.7090006@vmware.com>
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
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-11-05 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 11:59 KMS cursor BO semantics Thomas Hellstrom
2011-11-04 14:36 ` Ilija Hadzic
2011-11-04 14:38 ` Thomas Hellstrom
2011-11-04 15:34 ` Daniel Vetter
2011-11-04 22:30 ` Thomas Hellstrom
2011-11-04 22:49 ` Maarten Maathuis
2011-11-04 22:59 ` Thomas Hellstrom
2011-11-04 23:20 ` Maarten Maathuis
2011-11-05 16:10 ` Daniel Vetter [this message]
2011-11-07 10:26 ` Thomas Hellstrom
2011-11-11 18:17 ` James Simmons
2011-11-11 19:10 ` Maarten Maathuis
2011-11-11 19:14 ` Maarten Maathuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111105161034.GA2942@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox