On Tuesday, October 8, 2019 6:16 PM, Daniel Vetter wrote:
> On Tue, Oct 8, 2019 at 5:11 PM Simon Ser cont...@emersion.fr wrote:
>
> > On Tuesday, October 8, 2019 6:03 PM, Daniel Vetter dan...@ffwll.ch wrote:
> >
> > > > > > > In any case, this doesn't change the patch itself. Probably
> > > > >
On Tue, Oct 8, 2019 at 5:11 PM Simon Ser wrote:
>
> On Tuesday, October 8, 2019 6:03 PM, Daniel Vetter wrote:
>
> > > > > > In any case, this doesn't change the patch itself. Probably
> > > > > > something worth
> > > > > > mentionning in the commit message.
> > > > >
> > > > > Yes, recording
On Tuesday, October 8, 2019 6:03 PM, Daniel Vetter wrote:
> > > > > In any case, this doesn't change the patch itself. Probably something
> > > > > worth
> > > > > mentionning in the commit message.
> > > >
> > > > Yes, recording these use cases would be very nice.
> > >
> > > There's a lot
On Tue, Oct 8, 2019 at 1:39 PM Pekka Paalanen wrote:
>
> On Tue, 8 Oct 2019 11:59:04 +0200
> Daniel Vetter wrote:
>
> > On Mon, Sep 30, 2019 at 10:07:07AM +0300, Pekka Paalanen wrote:
> > > On Sun, 29 Sep 2019 20:30:44 +
> > > Simon Ser wrote:
> > >
> > > > Hi,
> > > >
> > > > > On Mon, Sep
On Tue, 8 Oct 2019 11:59:04 +0200
Daniel Vetter wrote:
> On Mon, Sep 30, 2019 at 10:07:07AM +0300, Pekka Paalanen wrote:
> > On Sun, 29 Sep 2019 20:30:44 +
> > Simon Ser wrote:
> >
> > > Hi,
> > >
> > > > On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> > > > >
On Mon, Sep 30, 2019 at 10:07:07AM +0300, Pekka Paalanen wrote:
> On Sun, 29 Sep 2019 20:30:44 +
> Simon Ser wrote:
>
> > Hi,
> >
> > > On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> > > > Currently the property docs don't specify whether it's okay for two
> > > > planes to
On Sun, 29 Sep 2019 20:30:44 +
Simon Ser wrote:
> Hi,
>
> > On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> > > Currently the property docs don't specify whether it's okay for two
> > > planes to
> > > have the same zpos value and what user-space should expect in this case.
Hi,
> On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> > Currently the property docs don't specify whether it's okay for two planes
> > to
> > have the same zpos value and what user-space should expect in this case.
> >
> > The rule mentionned in the past was to disambiguate with
On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> Currently the property docs don't specify whether it's okay for two planes to
> have the same zpos value and what user-space should expect in this case.
>
> The rule mentionned in the past was to disambiguate with object IDs. However
>
On Tuesday, September 24, 2019 11:48 AM, Pekka Paalanen
wrote:
> On Tue, 24 Sep 2019 07:34:30 +
> Simon Ser cont...@emersion.fr wrote:
>
> > On Tuesday, September 24, 2019 10:26 AM, Pekka Paalanen ppaala...@gmail.com
> > wrote:
> >
> > > On Mon, 23 Sep 2019 12:39:20 +
> > > Simon Ser
On Tue, 24 Sep 2019 07:34:30 +
Simon Ser wrote:
> On Tuesday, September 24, 2019 10:26 AM, Pekka Paalanen
> wrote:
>
> > On Mon, 23 Sep 2019 12:39:20 +
> > Simon Ser cont...@emersion.fr wrote:
> >
> > > Currently the property docs don't specify whether it's okay for two
> > >
On Tuesday, September 24, 2019 10:26 AM, Pekka Paalanen
wrote:
> On Mon, 23 Sep 2019 12:39:20 +
> Simon Ser cont...@emersion.fr wrote:
>
> > Currently the property docs don't specify whether it's okay for two planes
> > to
> > have the same zpos value and what user-space should expect in
On Mon, 23 Sep 2019 12:39:20 +
Simon Ser wrote:
> Currently the property docs don't specify whether it's okay for two planes to
> have the same zpos value and what user-space should expect in this case.
>
> The rule mentionned in the past was to disambiguate with object IDs. However
> some
Currently the property docs don't specify whether it's okay for two planes to
have the same zpos value and what user-space should expect in this case.
The rule mentionned in the past was to disambiguate with object IDs. However
some drivers break this rule (that's why the ordering is documented
14 matches
Mail list logo
