<div class="gmail_quote">On Mon, Nov 19, 2012 at 12:00 PM, Bill Spitzak <<a href="mailto:spitzak@gmail.com" target="_blank">spitzak@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">Pekka Paalanen wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> There have been complaints, that current Mesa does not work for software rendering in the Wayland stack, but I don't really know about that. It seems to be an uninteresting topic for Wayland devs (me included). </blockquote> </div> It does sound like <a href="https://bugs.freedesktop.org/show_bug.cgi?id=56741" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=56741</a> Do you have any explanation as to why the *shell* works? It is using EGL to composite. I can run an arbitrary number of simple_shm programs and it manages to composite them just fine. Also why does "flower" work exactly once? It does seem like this may be easy to fix by changing how the egl buffers are allocated. I would say this is a pretty major problem for Wayland. For a lot of people interested in developing the wayland api, software rendering is the only thing that works while still being able to run the development environment. </blockquote><div> 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 <a href="https://bugs.freedesktop.org/show_bug.cgi?id=54576">https://bugs.freedesktop.org/show_bug.cgi?id=54576</a> Scott </div></div>