From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Jesse Barnes <jesse.barnes@intel.com>,
Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: Allow legacy interface for legacy Y tiled display
Date: Wed, 01 Apr 2015 07:45:00 -0700 [thread overview]
Message-ID: <551C046C.9030907@virtuousgeek.org> (raw)
In-Reply-To: <20150401122811.GE25832@nuc-i3427.alporthouse.com>
On 04/01/2015 05:28 AM, Chris Wilson wrote:
> On Wed, Apr 01, 2015 at 02:20:53PM +0200, Daniel Vetter wrote:
>> On Wed, Apr 01, 2015 at 10:53:45AM +0100, Tvrtko Ursulin wrote:
>>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>>
>>> Makes it easier for userspace to start supporting Y tiled display,
>>> for at least the legacy format.
>>>
>>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>>
>> For the record: The point here is that we'll get a user for fb modifiers
>> by enabling Y tiling, not enabling Y tiling itself ... On that goal this
>> patch falls short, so nacked.
>
> Seriously? There is an existing client ready to use Y tiling framebuffers.
> There are none prepared to use the new api. Wishing will not change the
> inertia inherent in userspace.
Yeah I'm not sure I understand the objection either... we want to use
the new interface exclusively so this patch is nacked?
Jesse
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-01 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 9:53 [PATCH] drm/i915: Allow legacy interface for legacy Y tiled display Tvrtko Ursulin
2015-04-01 12:20 ` Daniel Vetter
2015-04-01 12:28 ` Chris Wilson
2015-04-01 14:45 ` Jesse Barnes [this message]
2015-04-02 12:31 ` shuang.he
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=551C046C.9030907@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=jesse.barnes@intel.com \
--cc=tvrtko.ursulin@intel.com \
--cc=tvrtko.ursulin@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.