<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa opengles Peppa Pig and openggles2 smurfs on Radeon PowerPC and PPC64" href="https://bugs.freedesktop.org/show_bug.cgi?id=99638#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Mesa opengles Peppa Pig and openggles2 smurfs on Radeon PowerPC and PPC64" href="https://bugs.freedesktop.org/show_bug.cgi?id=99638">bug 99638</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=99638#c7">comment #7</a>) > At a blind guess, I'm going to say that this is because Wayland's formats > are defined as DRM's are, i.e. explicitly little-endian where pixels are > accessed whole, rather than GL's byte-by-byte. I suppose the conversion > between GL and Wayland/DRM formats are simply broken for BE. A quick glance at platform_wayland.c shows this: static EGLBoolean dri2_wl_add_configs_for_visuals(_EGLDriver *drv, _EGLDisplay *disp) { struct dri2_egl_display *dri2_dpy = dri2_egl_display(disp); static const struct { const char *format_name; int has_format; unsigned int rgba_masks[4]; } visuals[] = { { "XRGB8888", HAS_XRGB8888, { 0xff0000, 0xff00, 0x00ff, 0xff000000 } }, { "ARGB8888", HAS_ARGB8888, { 0xff0000, 0xff00, 0x00ff, 0 } }, { "RGB565", HAS_RGB565, { 0x00f800, 0x07e0, 0x001f, 0 } }, }; Which seems like it could be off for BE... I happen to have a PPC G5 with a NV34/AGP sitting in it. I might try to play with it later (got it all to work with X11 again a while back). Although I'd have to get help with the wayland part of it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>