The DRM core setplane code should check that the plane is usable on the
specified CRTC before calling into the driver.
Prior to this patch, a plane's possible_crtcs field was purely
informational for userspace and was never actually verified at the
kernel level (aside from the primary plane
On Wed, Apr 23, 2014 at 10:03:59AM -0700, Matt Roper wrote:
The DRM core setplane code should check that the plane is usable on the
specified CRTC before calling into the driver.
Prior to this patch, a plane's possible_crtcs field was purely
informational for userspace and was never actually
On Wed, Apr 23, 2014 at 08:03:50PM +0200, Daniel Vetter wrote:
On Wed, Apr 23, 2014 at 10:03:59AM -0700, Matt Roper wrote:
The DRM core setplane code should check that the plane is usable on the
specified CRTC before calling into the driver.
Prior to this patch, a plane's possible_crtcs
On Wed, Apr 23, 2014 at 11:26:04AM -0700, Matt Roper wrote:
On Wed, Apr 23, 2014 at 08:03:50PM +0200, Daniel Vetter wrote:
On Wed, Apr 23, 2014 at 10:03:59AM -0700, Matt Roper wrote:
The DRM core setplane code should check that the plane is usable on the
specified CRTC before calling into
