On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen <tomi.valkeinen@xxxxxx> wrote: > 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. I'd like to think we could make DRM the underlying display framework; it already exposes an fb interface, and with overlays, a bit more of the v4l2 stuff is done as well. Certainly eliminating three copies of mode setting infrastructure would be nice... > 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. Those are split between the DRM layer and the underlying device driver, which provides both kernel (via fb) and user space 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. We integrate the panel (and other video output) drivers into the device drivers. With desktop chips, they're not easily separable. None of the desktop output drivers are simple; things like DisplayPort require link training, and everyone needs EDID. We share some of that code in the DRM layer today, and it would be nice to share even more. We should figure out if the DRM interfaces are sufficient for your needs; they're pretty flexible at this point. Of course, backlight remains a mess in the desktop world; with many custom backlight drivers along with generic ACPI and then per-video-device drivers as well. -- keith.packard@xxxxxxxxx
Attachment:
pgpDOaTuQsm_m.pgp
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
