linux-kernel - Re: [PATCH] drm: DON'T require each CRTC to have a unique primary plane

Open Source and information security mailing list archives

Date:   Mon, 29 Mar 2021 11:15:33 +0300
From:   Pekka Paalanen <ppaalanen@...il.com>
To:     Paul Cercueil <paul@...pouillou.net>
Cc:     Simon Ser <contact@...rsion.fr>,
        Thomas Zimmermann <tzimmermann@...e.de>,
        David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
        od@...c.me, dri-devel@...ts.freedesktop.org, stable@...r.kernel.org
Subject: Re: [PATCH] drm: DON'T require each CRTC to have a unique primary
 plane

On Sat, 27 Mar 2021 11:26:26 +0000
Paul Cercueil <paul@...pouillou.net> wrote:

> It has two mutually exclusive background planes (same Z level) + one 
> overlay plane.

What's the difference between the two background planes?

How will generic userspace know to pick the "right" one?

Thanks,
pq

> Le sam. 27 mars 2021 à 11:24, Simon Ser <contact@...rsion.fr> a écrit 
> :
> > On Saturday, March 27th, 2021 at 12:22 PM, Paul Cercueil 
> > <paul@...pouillou.net> wrote:
> >   
> >>  The ingenic-drm driver has two mutually exclusive primary planes
> >>  already; so the fact that a CRTC must have one and only one primary
> >>  plane is an invalid assumption.  
> > 
> > Why does this driver expose two primary planes, if it only has a 
> > single
> > CRTC?  
> 
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@...ts.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

Content of type "application/pgp-signature" skipped

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives