Bugzilla – Bug 60212
[Bisected] Weston black output
Last modified: 2013-02-04 18:31:03 UTC
With latest mesa on Sandybridge, the weston output is black with cursor. This is true for both x11 and drm backends. Weston nor weston-desktop-shell crashes and the compositor is fully functional. I bisected to find this as the culprit:
11f5c82e8383fff00edd943209100cc1c9a1424b is the first bad commit
Author: Abdiel Janulgue <firstname.lastname@example.org>
Date: Wed Nov 28 15:10:33 2012 +0200
intel: Create a miptree using offsets in intel_set_texture_image_region
When binding a region to a texture image, re-create the miptree base-level
considering the offset and dimension information exported by DRIImage.
v8: - Move the alignment surface address checks from the image-from-texture
code to the texture-from-image side. This allows the error reporting to conform to
OES_EGL_Image and to prevent mixing up EGL and GL errors. Reported by Chad Versace.
- Addressed an existing issue in renderbuffer case where there is a
a possibility of creating EGL images out of depthstencil textures which isn't
really possible. This was spotted by Eric earlier.
Reviewed-by: Eric Anholt <email@example.com> (v6)
Reviewed-by: Chad Versace <firstname.lastname@example.org> (v8)
Signed-off-by: Abdiel Janulgue <email@example.com>
:040000 040000 357888e370259225fda01324625fc78c3186de93 71e6725f72609e2018b40f0a9cce976d0d18a04a M src
I am not sure if this only affects i965 but I am posting it here since it's the driver I am using. This is with latest wayland stack from git.
Created attachment 74168 [details] [review]
Ok. I forgot to setup the dimension in the image from planar setup which is the likely cause of this issue. Please try the attach patch which should fix this case.
this was just tested by me, meaning it works now as expected:
Tested-by: Tiago Vignatti <firstname.lastname@example.org>
(In reply to comment #1)
> Created attachment 74168 [details] [review] [review]
> Proposed fix
> Ok. I forgot to setup the dimension in the image from planar setup which is
> the likely cause of this issue. Please try the attach patch which should fix
> this case.
Hi, thanks for the quick response. This patch fixes the problem here as well.
Tested-by: Scott Moreau <email@example.com>
Abdiel, when you begin working on a bug, please assign it to yourself. If you leave the bug in the NEW state, someone may begin working on it, duplicating your efforts.
Fix is now applied to master.
Change to RESOLVED/FIXED.