From: "Michel Dänzer" <michel@daenzer.net>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm: add DRM_CAPs for cursor size
Date: Thu, 13 Feb 2014 10:37:52 +0900 [thread overview]
Message-ID: <1392255472.24291.11.camel@thor.local> (raw)
In-Reply-To: <1392229733-1379-1-git-send-email-alexander.deucher@amd.com>
On Mit, 2014-02-12 at 13:28 -0500, Alex Deucher wrote:
> Some hardware may not support standard 64x64 cursors. Add
> a drm cap to query the cursor size from the kernel. Some examples
> include radeon CIK parts (128x128 cursors) and armada (32x64 or 64x32).
> This allows things like device specific ddxes to remove asics specific
> logic and also allows xf86-video-modesetting to work properly with hw
> cursors on this hardware. Default to 64 if the driver doesn't specify
> a size.
The patches look good, but what's your plan for dealing with other KMS
apps such as Wayland compositors (weston is also affected by this, I
assume so is gnome-shell, maybe more)? I was thinking it might be good
to have a backup plan in the kernel, e.g. copying from the BO passed in
by userspace to a different BO if the former doesn't match the hardware
size.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-02-13 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 18:28 [PATCH 1/2] drm: add DRM_CAPs for cursor size Alex Deucher
2014-02-12 18:28 ` [PATCH 2/2] drm/radeon: fill in " Alex Deucher
2014-02-12 18:28 ` [PATCH] modesetting: query cursor size from the kernel Alex Deucher
2014-02-13 1:37 ` Michel Dänzer [this message]
2014-02-14 2:21 ` [PATCH 1/2] drm: add DRM_CAPs for cursor size Alex Deucher
2014-02-14 21:02 ` Rob Clark
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=1392255472.24291.11.camel@thor.local \
--to=michel@daenzer.net \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
/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