On Aug 14, 2012, at 11:21 PM, Scott Moreau wrote: > That looks like a driver bug to me
Any hints where to look? Is this in Mesa? Is it in the "gallium" subdirectory of mesa? I grepped for the word "stride" but it occurs hundreds of times. My best guess as to what is happening is that the stride was calculated by rounding the surface width up to the next multiple of 16, and this stride is used to allocate the memory and to draw *into* the buffer. However when the buffer is read for compositing into the final output, it ignores the stride and uses the width. Also why are wl_egl calls in mesa? The source code seems to not show any reason for them to be there rather than in wayland. I think it would make a lot more sense for them to be in wayland and it certainly looks possible. _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
