On Thu, 15 Sep 2011 17:12:43 +0000, Florian Tobias Schandinat <FlorianSchandinat@xxxxxx> wrote: > Interesting that this comes from the people that pushed the latest mode setting > code into the kernel. But I don't think that this will happen, the exposed user > interfaces will be around for decades and the infrastructure code could be > shared, in theory. We moved mode setting code from user space to kernel space -- the DRM stuff comes directly from X, which has a fairly long history of complicated display environments. The DRM code does expose fb interfaces to both kernel and user mode, figuring out how to integrate v4l2 and drm seems like the remaining challenge. > For fb and V4L2 I think we'll develop some level of interoperability, share > concepts and maybe even some code. The FOURCC pixel formats and overlays are > such examples. As Laurent is really interested in it I think we can get some > nice progress here. Jesse's design for the DRM overlay code will expose the pixel formats as FOURCC codes so that DRM and v4l2 can interoperate -- we've got a lot of hardware that has both video decode and 3D acceleration, so those are going to get integrated somehow. And, we have to figure out how to share buffers between these APIs to avoid copying data with the CPU. DRM provides fb interfaces, so you don't need to change fb at all -- hardware that requires the capabilities provided by DRM will use that and not use any of the other fb code in the kernel. -- keith.packard@xxxxxxxxx
Attachment:
pgpyhyvBGZG47.pgp
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
