On Mon, 10 Sep 2018 11:16:03 +0200
Dirk Eibach wrote:
> I did a git bisect and found the commit "244244d1 (refs/bisect/bad)
> compositor-drm: Use GBM modifier API" introduced the problem.
Hi,
ok. I wonder if there is something wrong with Mesa/GBM/Nouveau, since
it is generic code in Weston and
On Mon, 10 Sep 2018 10:12:18 +0200
Dirk Eibach wrote:
> Perhaps I should add, that with rolling back to weston 4.0.0.
> everything works fine. So nouveau support must have been broken
> somewhere inbetween.
Hi,
right, so it's a regression. Weston does not have code specific to
Nouveau, but it d
I did a git bisect and found the commit "244244d1 (refs/bisect/bad)
compositor-drm: Use GBM modifier API" introduced the problem.
Am Mo., 10. Sep. 2018 um 10:12 Uhr schrieb Dirk Eibach
:
>
> Perhaps I should add, that with rolling back to weston 4.0.0.
> everything works fine. So nouveau support mu
Perhaps I should add, that with rolling back to weston 4.0.0.
everything works fine. So nouveau support must have been broken
somewhere inbetween.
Am Mo., 10. Sep. 2018 um 08:59 Uhr schrieb Dirk Eibach
:
>
> > Looks like some drm issue. Just wondering if you can use KMS APIs directly
> > without s
> Looks like some drm issue. Just wondering if you can use KMS APIs directly
> without seeing this issue? So for example, will kmscube draw something on the
> screen (https://github.com/robclark/kmscube)? BTW, noticed that you are using
> /dev/dri/card1 in your logs. What's at card0? Note that t
Looks like some drm issue. Just wondering if you can use KMS APIs directly
without seeing this issue? So for example, will kmscube draw something on the
screen (https://github.com/robclark/kmscube)? BTW, noticed that you are using
/dev/dri/card1 in your logs. What's at card0? Note that this kmsc
