From: Daniel Stone <daniel@fooishbar.org>
To: Rob Clark <robdclark@gmail.com>
Cc: "Kristian H. Kristensen" <hoegsberg@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH 1/2] drm: Add new DRM_IOCTL_MODE_GETPLANE2
Date: Tue, 4 Apr 2017 11:07:26 +0100 [thread overview]
Message-ID: <CAPj87rNZFMiyRBoO6v_zXWdGTnV2D-YV6DOf7W0u9eVq-N+rOQ@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGuB=sy94hJRijaKKwE-NQ9oyZjQt5feDEFY7=VXZx=oNQ@mail.gmail.com>
Hi,
On 1 April 2017 at 19:47, Rob Clark <robdclark@gmail.com> wrote:
> On Tue, Dec 20, 2016 at 7:12 PM, Kristian H. Kristensen
> <hoegsberg@gmail.com> wrote:
>> This new ioctl exctends DRM_IOCTL_MODE_GETPLANE, by returning
>> information about the modifiers that will work with each format.
>
> So, just to toss out a completely different idea..
>
> What if instead of a new ioctl, we had a read-only blob property
> (which encoded the info basically the same way, plus the fourcc's)?
>
> If we do writeback via some sort of OUT_FB_ID property on plane/crtc,
> we will need the same sort of format information so userspace knows
> what output formats (and modifiers) are supported. So re-using the
> same blob property layout (and userspace parsing) seems useful.
I'd definitely be cool with this. It doesn't make our lives any easier
or more difficult in terms of parsing, and it also avoids a dep on new
libdrm API/ABI, which is always nice. If anyone types this up, I'll
happily port the Weston WIP.
Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-04 10:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 0:12 [PATCH 1/2] drm: Add new DRM_IOCTL_MODE_GETPLANE2 Kristian H. Kristensen
2016-12-21 0:12 ` [PATCH 2/2] i915: Add format modifiers for Intel Kristian H. Kristensen
2016-12-21 0:46 ` [PATCH 1/2] drm: Add new DRM_IOCTL_MODE_GETPLANE2 Rob Clark
2016-12-21 9:15 ` Daniel Vetter
2016-12-21 9:19 ` Ville Syrjälä
2016-12-21 15:42 ` Rob Clark
2016-12-21 17:26 ` Kristian Høgsberg
2016-12-22 7:04 ` Daniel Vetter
2016-12-21 15:41 ` Rob Clark
2016-12-21 18:03 ` Kristian H. Kristensen
2017-01-03 6:42 ` Daniel Kurtz
2017-04-01 18:47 ` Rob Clark
2017-04-03 21:44 ` Rob Clark
2017-04-04 10:07 ` Daniel Stone [this message]
2017-04-04 19:41 ` Ben Widawsky
2017-04-28 12:11 ` Lucas Stach
2017-04-28 18:33 ` Ben Widawsky
2017-05-02 12:48 ` Lucas Stach
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=CAPj87rNZFMiyRBoO6v_zXWdGTnV2D-YV6DOf7W0u9eVq-N+rOQ@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=benjamin.widawsky@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@gmail.com \
--cc=robdclark@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.