[RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality.
ppaalanen at gmail.com
Thu Apr 13 07:44:38 UTC 2017
On Tue, 11 Apr 2017 13:23:53 +0200
Gerd Hoffmann <kraxel at redhat.com> wrote:
> > > Just let know what you need tested, I should be able to turn it around
> > > within a couple of days.
> > That's part of my problem. I don't really know what should be tested.
> > What do people do with their BE machines that we should avoid breaking?
> For the virtual machine use case the bar is pretty low, it's mostly
> about a graphical server console. Anaconda installer. Gnome desktop
> with browser and standard xorg (xterm) + gtk apps. No heavy OpenGL
> stuff. No hardware acceleration, so if opengl is used then it'll be
> Right now Xorg is important. Not sure whenever wayland ever will be,
> possibly the ppc64 -> ppc64le switch goes faster than the xorg ->
> wayland switch.
IMHO you can ignore Wayland for now I suppose, I just wanted to point
out that we have similar problems there and whatever you do with the
DRM format codes will affect things on Wayland too.
Once you get things hashed out on an X.org based stack, we can look
what it means for Wayland software.
After all, BE users are scarce and allegedly favouring old software to
avoid breakage; Wayland is new, and Wayland compositors still "rare",
so the intersection of people using both BE and Wayland and relying on
it to work is... minuscule? insignificant?
I don't mean to belittle people that use Wayland on BE, but by that one
bug report EGL is and probably has been broken, and it's unclear if
anything has ever worked.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the dri-devel