From: Daniel Vetter <daniel@ffwll.ch>
To: Daniel Stone <daniel@fooishbar.org>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Thierry Reding <thierry.reding@avionic-desi.gn.de>
Subject: Re: [RFC] drm/i915: Render decompression support for Gen9 and above
Date: Tue, 26 Jan 2016 10:43:06 +0100 [thread overview]
Message-ID: <CAKMK7uFz6osri86dDy=QDtNLxN3=kiZWcDRTjEaTALk6MKvrPg@mail.gmail.com> (raw)
In-Reply-To: <CAPj87rOj+D1AD5=P3B9wE67Z9YvJ3=182ZSvdvFheQxHuq1gfw@mail.gmail.com>
On Mon, Jan 25, 2016 at 8:09 PM, Daniel Stone <daniel@fooishbar.org> wrote:
>>> The property-based design precludes optimal use of current open-source userspace.
>> I don’t see how it even effects open-source userspace. It can just ignore it entirely.
>
> i.e. this property is useless for open-source userspace, which can
> never hint that render compression has been resolved. So fine by me if
> you want to merge it I guess, and we'll just ignore it.
New ABI requires open-source userspace. If it's not suitable for that
it won't land.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-01-26 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 19:42 [RFC] drm/i915: Render decompression support for Gen9 and above Vandana Kannan
2015-09-07 16:35 ` Daniel Vetter
2015-09-08 22:07 ` Jesse Barnes
2015-09-09 15:23 ` Daniel Vetter
2015-09-09 15:24 ` Jesse Barnes
2015-09-09 16:36 ` Smith, Gary K
2015-09-09 17:04 ` Jesse Barnes
2015-09-10 15:02 ` Daniel Vetter
2016-01-19 10:28 ` Daniel Stone
2016-01-25 17:38 ` Jesse Barnes
2016-01-25 18:15 ` Smith, Gary K
2016-01-25 18:37 ` Daniel Stone
2016-01-25 19:04 ` Smith, Gary K
2016-01-25 19:08 ` Smith, Gary K
2016-01-25 19:09 ` Daniel Stone
2016-01-26 9:43 ` Daniel Vetter [this message]
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='CAKMK7uFz6osri86dDy=QDtNLxN3=kiZWcDRTjEaTALk6MKvrPg@mail.gmail.com' \
--to=daniel@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thierry.reding@avionic-desi.gn.de \
/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.