From: Daniel Stone <daniel@fooishbar.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 1/3] drm: Add new DRM_IOCTL_MODE_GETPLANE2
Date: Fri, 13 Jan 2017 09:45:25 +0000 [thread overview]
Message-ID: <CAPj87rPB02p7UzKRWL9xaSECxKJVpEayy0QqKfXdNhC5JspuzA@mail.gmail.com> (raw)
In-Reply-To: <20170113093751.GF31595@intel.com>
Hey,
On 13 January 2017 at 09:37, Ville Syrjälä
<ville.syrjala@linux.intel.com> wrote:
> On Thu, Jan 12, 2017 at 07:27:03PM +0000, Daniel Stone wrote:
>> It would make sense, but then gbm_surface_create_with_modifiers takes
>> a fixed pixel format and a list of acceptable modifiers (which to me
>> seems like the right way around as an API), so whenever I was creating
>> a surface, I'd have to walk through and create a new list, flipped
>> back the other way.
>
> Yeah, for that your original order makes more sense, even if it
> potentially uses more memory.
Given the size of framebuffers, I'm really not concerned by the
in-memory size of a format list. :)
Cheers,
Daniel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-01-13 9:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 0:51 [PATCH 0/3] GET_PLANE2 w/ i915 implementation Ben Widawsky
2017-01-12 0:51 ` [PATCH 1/3] drm: Add new DRM_IOCTL_MODE_GETPLANE2 Ben Widawsky
2017-01-12 1:43 ` [Intel-gfx] " Rob Clark
2017-01-12 9:38 ` Ville Syrjälä
2017-01-12 14:56 ` Rob Clark
2017-01-12 17:04 ` Daniel Stone
2017-01-12 17:45 ` Ville Syrjälä
2017-01-12 17:50 ` Daniel Stone
2017-01-12 18:11 ` Ville Syrjälä
2017-01-12 19:27 ` Daniel Stone
2017-01-13 9:37 ` [Intel-gfx] " Ville Syrjälä
2017-01-13 9:45 ` Daniel Stone [this message]
2017-01-12 10:23 ` Ville Syrjälä
2023-11-24 15:08 ` Andy Shevchenko
2017-01-25 5:20 ` [PATCH 1/3] [v2] " Ben Widawsky
2017-01-25 15:28 ` Ville Syrjälä
2017-01-26 23:34 ` [PATCH 1/3] [v3] " Ben Widawsky
2017-01-12 0:51 ` [PATCH 2/3] drm/i915: Add format modifiers for Intel Ben Widawsky
2017-01-12 10:51 ` Ville Syrjälä
2017-01-12 18:00 ` Ben Widawsky
2017-01-12 18:32 ` Ville Syrjälä
2017-01-12 18:56 ` Ben Widawsky
2017-01-13 9:35 ` Ville Syrjälä
2017-01-12 0:51 ` [PATCH 3/3] drm/i915: Add support for GET_PLANE2 CCS modifiers Ben Widawsky
2017-01-12 1:01 ` ✗ Fi.CI.BAT: failure for GET_PLANE2 w/ i915 implementation Patchwork
2017-01-12 1:23 ` Ben Widawsky
2017-01-25 6:32 ` ✗ Fi.CI.BAT: failure for GET_PLANE2 w/ i915 implementation (rev2) Patchwork
2017-01-27 1:02 ` ✗ Fi.CI.BAT: failure for GET_PLANE2 w/ i915 implementation (rev3) Patchwork
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=CAPj87rPB02p7UzKRWL9xaSECxKJVpEayy0QqKfXdNhC5JspuzA@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=ben@bwidawsk.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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.