From: Adam Jackson <ajax@redhat.com>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>, Dave Airlie <airlied@redhat.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:DRM DRIVER FOR QEMU'S CIRRUS DEVICE"
<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] drm/cirrus: rewrite and modernize driver.
Date: Wed, 03 Apr 2019 11:52:31 -0400 [thread overview]
Message-ID: <eba84e1ed570908acdf65a2683b77718ff585e99.camel@redhat.com> (raw)
In-Reply-To: <CAPj87rOE2K9nxV2p+KrMTDnijdKpmNP8BGSUJyK9YtFueJpkqw@mail.gmail.com>
On Wed, 2019-04-03 at 16:15 +0100, Daniel Stone wrote:
> There's already a list of supported formats for each DRM plane, which
> you can get via drmModeGetPlane (being careful to enable universal
> planes so you can discover the primary plane). The same information is
> present in the 'IN_FORMATS' property, which is more difficult to parse
> but also tells you about modifiers.
>
> modesetting already pulls all this out (at least in the atomic path)
> so we can reason about acceptable modifiers.
D'oh, I knew that. The problem then is modesetting isn't pulling that
info out early enough in PreInit. I'll consider that another case of
xorg/xserver#9 then.
- ajax
next prev parent reply other threads:[~2019-04-03 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 7:23 [PATCH] drm/cirrus: rewrite and modernize driver Gerd Hoffmann
2019-04-03 7:47 ` Daniel Vetter
2019-04-03 8:53 ` Gerd Hoffmann
2019-04-03 9:58 ` Noralf Trønnes
2019-04-03 10:27 ` Gerd Hoffmann
2019-04-03 15:12 ` Adam Jackson
2019-04-03 15:15 ` Daniel Stone
2019-04-03 15:52 ` Adam Jackson [this message]
2019-04-04 2:58 ` David Airlie
2019-04-04 5:50 ` Gerd Hoffmann
2019-04-04 6:31 ` Daniel Vetter
2019-04-04 7:09 ` Gerd Hoffmann
2019-04-04 8:30 ` Gerd Hoffmann
2019-04-04 8:52 ` Daniel Vetter
2019-04-04 10:06 ` Noralf Trønnes
2019-04-04 10:27 ` Gerd Hoffmann
2019-04-04 11:45 ` Noralf Trønnes
2019-04-04 11:45 ` Gerd Hoffmann
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=eba84e1ed570908acdf65a2683b77718ff585e99.camel@redhat.com \
--to=ajax@redhat.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).