On Thu, 2011-09-15 at 09:59 -0500, Keith Packard wrote: > On Thu, 15 Sep 2011 15:07:05 +0300, Tomi Valkeinen <tomi.valkeinen@xxxxxx> wrote: > > > This was a very rough and quite short proposal, but I'm happy to improve > > and extend it if it's not totally shot down. > > Jesse Barnes has put together a proposal much like this to work within > the existing DRM environment. This is pretty much the last piece of > missing mode-setting functionality that we know of, making DRM capable > of fully supporting existing (and planned) devices. > > Here's a link to some older discussion on the issue, things have changed > a bit since then and we had a long talk about this during the X > Developers' Conference this week in Chicago. Expect an update to his > proposal in the coming weeks. > > http://lists.freedesktop.org/archives/dri-devel/2011-April/010559.html > Thanks for the link. Right, DRM has already components I described in my proposal, and adding overlays brings it even closer. However, I think there are two major differences: 1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if the plan is to make DRM the core Linux display framework, upon which everything else is built, and fb and v4l2 are changed to use DRM. But even if it was done like that, I see that it's combining two separate things: 1) the lower level HW control, and 2) the upper level buffer management, policies and userspace interfaces. 2) It's missing the panel driver part. This is rather important on embedded systems, as the panels often are not "dummy" panels, but they need things like custom initialization, sending commands to adjust backlight, etc. Tomi _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
