On Mon, Mar 03, 2014 at 07:24:04PM +0100, David Herrmann wrote:
> How can user-space distinguish primary-planes from others? With
> atomic-modesetting I can understand that there's no need to
> distinguish them, but without it, we need to know which planes not to
> use. Same problem for the
Hi
On Thu, Feb 27, 2014 at 11:14 PM, Matt Roper
wrote:
> Allow drivers to provide a drm_plane structure corresponding to a CRTC's
> primary plane. These planes will be included in the plane list for any
> clients setting the DRM_CLIENT_CAP_EXPOSE_PRIMARY_PLANES capability bit.
>
>
On Mon, Mar 03, 2014 at 09:45:53AM -0800, Matt Roper wrote:
> On Mon, Mar 03, 2014 at 03:47:43PM +, Damien Lespiau wrote:
> > On Thu, Feb 27, 2014 at 02:14:40PM -0800, Matt Roper wrote:
> > > Allow drivers to provide a drm_plane structure corresponding to a CRTC's
> > > primary plane. These
On Thu, Feb 27, 2014 at 02:14:40PM -0800, Matt Roper wrote:
> Allow drivers to provide a drm_plane structure corresponding to a CRTC's
> primary plane. These planes will be included in the plane list for any
> clients setting the DRM_CLIENT_CAP_EXPOSE_PRIMARY_PLANES capability bit.
>
>
On Mon, Mar 03, 2014 at 03:47:43PM +, Damien Lespiau wrote:
> On Thu, Feb 27, 2014 at 02:14:40PM -0800, Matt Roper wrote:
> > Allow drivers to provide a drm_plane structure corresponding to a CRTC's
> > primary plane. These planes will be included in the plane list for any
> > clients setting
Allow drivers to provide a drm_plane structure corresponding to a CRTC's
primary plane. These planes will be included in the plane list for any
clients setting the DRM_CLIENT_CAP_EXPOSE_PRIMARY_PLANES capability bit.
Signed-off-by: Matt Roper
---
drivers/gpu/drm/drm_crtc.c | 168
