From: Daniel Vetter <daniel@ffwll.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
rob.clark@linaro.org
Subject: Re: [PATCH] DRM planes
Date: Thu, 3 Nov 2011 19:58:11 +0100 [thread overview]
Message-ID: <20111103185811.GD2970@phenom.ffwll.local> (raw)
In-Reply-To: <20111103174743.0c91a4c1@lxorguk.ukuu.org.uk>
On Thu, Nov 03, 2011 at 05:47:43PM +0000, Alan Cox wrote:
> > In short decoding these fourcc values with all their implicit assumptions
> > about offset, strides and whatnotelse will be one giant switch mess. Not
> > my idea of a nice kernel interface. Also practically guaranteed to result
> > in slightly different behaviour in each driver.
>
> So you'd rather make each applicationa author get it wrong individually
> and uniquely. That is a bigger mess by far.
We're talking about gpus, there's no way an application will talk to them
than through some nice cozy abstraction layer like OpenGl, X, ... Even
Wayland has gbm to do the low-level kms scanout allocation.
> > In conclusion: Ditch the addfb2ioctl and just add a few more kms pixel
> > formats for the new packed yuv layouts that the snb+ sprite code needs.
>
> If you need a decoder for some hardware then fine, write one - share it
> with the v4l one and put it in a library drivers can call.
>
> However - user space is already working in fourcc, v4l has working fourcc
> and dumping the mess on the user isn't going to be a win.
The mess will be dumped onto userspace anyway, but it won't be dumped onto
the user - that one should use Xv or some fancy EGLImage extension.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-11-03 18:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 20:03 [PATCH] DRM planes Jesse Barnes
2011-11-02 20:03 ` [PATCH 1/5] drm: add plane support Jesse Barnes
2011-11-02 22:33 ` Jesse Barnes
2011-11-03 18:21 ` Jesse Barnes
2011-11-03 22:48 ` Jesse Barnes
2011-11-03 22:56 ` Daniel Vetter
2011-11-04 2:22 ` Joonyoung Shim
2011-11-04 14:10 ` Jesse Barnes
2011-11-02 20:03 ` [PATCH 2/5] drm: add an fb creation ioctl that takes a pixel format Jesse Barnes
2011-11-03 18:22 ` Jesse Barnes
2011-11-04 7:34 ` Joonyoung Shim
2011-11-04 14:13 ` Jesse Barnes
[not found] ` <CAAQKjZPhqYdMAUkbCbc68muPLN7azuVr0yod7hFC=i+MigwNhw@mail.gmail.com>
2011-11-07 16:12 ` Jesse Barnes
2011-11-07 17:02 ` Rob Clark
2011-11-02 20:03 ` [PATCH 3/5] drm/i915: rename existing overlay support to "legacy" Jesse Barnes
2011-11-03 18:22 ` Jesse Barnes
2011-11-02 20:03 ` [PATCH 4/5] drm/i915: add SNB and IVB video sprite support Jesse Barnes
2011-11-03 18:22 ` Jesse Barnes
2011-11-04 2:29 ` [Intel-gfx] " Lan, Hai
2011-11-02 20:03 ` [PATCH 5/5] drm/i915: add destination color key support Jesse Barnes
2011-11-03 18:23 ` Jesse Barnes
2011-11-03 14:11 ` [PATCH] DRM planes Daniel Vetter
2011-11-03 15:12 ` Jesse Barnes
2011-11-03 17:29 ` Daniel Vetter
2011-11-03 17:36 ` Jesse Barnes
2011-11-03 18:55 ` Rob Clark
2011-11-03 19:14 ` Jesse Barnes
2011-11-03 17:47 ` Alan Cox
2011-11-03 18:58 ` Daniel Vetter [this message]
2011-11-03 22:20 ` Alan Cox
2011-11-03 22:24 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2011-11-07 18:02 Jesse Barnes
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=20111103185811.GD2970@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rob.clark@linaro.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 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.