Re: [PATCH] DRM planes

[Jesse Barnes <jbarnes@virtuousgeek.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]

On Thu, 3 Nov 2011 22:20:00 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > 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.
> 
> You are talking about scanouts. Nothing more. Nothing in KMS/DRM even
> requires GPU accelerations.
> 
> > > 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.
> 
> Or quite likely in many embedded circumstances be working directly with
> buffers and FourCC. Just like happens now with V4L. FourCC has its ugly
> corners but its trivial to turn it into a table if you have a driver that
> requires this. Old hat, old problem. Solved in AmigaOS in the 1980s.

Ok now does anyone want to provide reviewed-bys on this stuff so Dave
will feel warm & fuzzy before applying the patches?

Daniel, have you been beaten down enough to acquiesce to that?  Alan,
does this look usable for your stuff?

-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx