Problems with the newest wayland git

John Kåre Alsaker john.kare.alsaker at gmail.com
Mon Nov 19 11:40:36 PST 2012


On Mon, Nov 19, 2012 at 8:32 PM, Bill Spitzak <spitzak at gmail.com> wrote:
> Can somebody explain why compiling weston with the switch
> "--with-cairo-glesv2" would perhaps fix the weston clients (I am not at my
> machine to try this so I don't know if it does). Doesn't that switch *make*
> it use EGL rather than having cairo write to the image buffer?
It will try to use EGL and GLESv2 if that exists on the system and
fall back to wl_shm and cairo's image backend otherwise.

>
>
> Bill Spitzak wrote:
>>
>> Scott Moreau wrote:
>>
>>> I believe all open drivers should work with drm at this point. There was
>>> a nouveau kernel module bug that was recently fixed. The report can be found
>>> here https://bugs.freedesktop.org/show_bug.cgi?id=54576
>>
>>
>> Nouveau has a bug that makes x11-compositor very very slow (event-ready
>> returns false after each event is read for Wayland). This has remained true
>> through 4 versions of Ubuntu and every window manager I can think of. I
>> posted several emails here about it trying to get hints as to how to fix
>> this (I assume there is something x11-compositor can do, as I do not see
>> equivalent bugs in other programs).
>>
>> Despite the obvious slowness, software rendering on the Nvidia driver made
>> x11-compositor actually usable by avoiding this bug. Since I am interested
>> in trying to design parts of the client/server api of Wayland I do not think
>> I should be running it on a system with obvious synchronization error as
>> that could hide errors in the design.
>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel


More information about the wayland-devel mailing list