Display driver enhancement topics

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
Line 21: Line 21:
*** I'm a bit undecided at this point whether virtual overlays should/could all be hidden in the driver, or whether there should be a userspace component in the display server.  Typically, if you look at vaapi (libva) it is using a sort of extension to DRI to render frames of video, in a similar way to how flipping is handled for GL apps.  If we took this approach, then it could be the display server that decides to fall back to using virtual overlays.  I guess there must be some analogy to DRI for android.
*** I'm a bit undecided at this point whether virtual overlays should/could all be hidden in the driver, or whether there should be a userspace component in the display server.  Typically, if you look at vaapi (libva) it is using a sort of extension to DRI to render frames of video, in a similar way to how flipping is handled for GL apps.  If we took this approach, then it could be the display server that decides to fall back to using virtual overlays.  I guess there must be some analogy to DRI for android.
*** also, separation of buffer and pipe is needed in the case of virtual display spanning multiple monitors, so that video window can also span multiple monitors.
*** also, separation of buffer and pipe is needed in the case of virtual display spanning multiple monitors, so that video window can also span multiple monitors.
 +
** hotplug notification to userspace, and detection of monitor state (connected/disconnected) is also part of DRM
* Support MCF
* Support MCF

Revision as of 15:43, 7 March 2011


Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox