On Fri, Jul 09, 2021 at 12:08:14PM +0300, Pekka Paalanen wrote:
> On Fri, 9 Jul 2021 10:02:28 +0200
> Daniel Vetter wrote:
>
> > On Fri, Jul 09, 2021 at 10:24:44AM +0300, Pekka Paalanen wrote:
> > > On Tue, 6 Jul 2021 18:12:44 +0200
> > > Maxime Ripard wrote:
> > >
> > > > New KMS properties
On Fri, 9 Jul 2021 10:02:28 +0200
Daniel Vetter wrote:
> On Fri, Jul 09, 2021 at 10:24:44AM +0300, Pekka Paalanen wrote:
> > On Tue, 6 Jul 2021 18:12:44 +0200
> > Maxime Ripard wrote:
> >
> > > New KMS properties come with a bunch of requirements to avoid each
> > > driver from running their
On Fri, Jul 09, 2021 at 10:24:44AM +0300, Pekka Paalanen wrote:
> On Tue, 6 Jul 2021 18:12:44 +0200
> Maxime Ripard wrote:
>
> > New KMS properties come with a bunch of requirements to avoid each
> > driver from running their own, inconsistent, set of properties,
> > eventually leading to issues
On Tue, 6 Jul 2021 18:12:44 +0200
Maxime Ripard wrote:
> New KMS properties come with a bunch of requirements to avoid each
> driver from running their own, inconsistent, set of properties,
> eventually leading to issues like property conflicts, inconsistencies
> between drivers and semantics, e
On Tue, Jul 06, 2021 at 06:12:44PM +0200, Maxime Ripard wrote:
> New KMS properties come with a bunch of requirements to avoid each
> driver from running their own, inconsistent, set of properties,
> eventually leading to issues like property conflicts, inconsistencies
> between drivers and semanti
New KMS properties come with a bunch of requirements to avoid each
driver from running their own, inconsistent, set of properties,
eventually leading to issues like property conflicts, inconsistencies
between drivers and semantics, etc.
Let's document what we expect.
Cc: Alexandre Belloni
Cc: Al
