[PATCH 1/3] drm: fourcc byteorder: drop DRM_FORMAT_BIG_ENDIAN
kraxel at redhat.com
Tue May 2 15:06:31 UTC 2017
> I also think that this patch requires more comments than the
> commit message has at the moment.
> Removing the definition also removes the possibility to describe a lot
> of pixel formats, so that should definitely be mentioned. I think it
> would also be good to have some kind of justified claim that no
> hardware actually needs the pixel formats this is removing (e.g. RGB565
That and RGB2101010 BE are the only candidates I can think of.
Dealing with those in none-native byteorder is a PITA though. Display
hardware is little endian (pci byte order) for quite a while already.
> Maybe this was already in the long discussions, but I feel it
> should be summarized in the commit message.
Radeon and nvidia (nv40) cards where mentioned. I'll try to summarize
(feel free to correct me if I'm wrong).
nvidia has support for 8 bit-per-color formats only on bigendian hosts.
Not sure whenever this is a driver or hardware limitation.
radeon looks differently on pre-R600 and R600+ hardware.
pre-R600 can byteswap on cpu access, so the cpu view is bigendian
whereas things are actually stored on little endian byte order.
Hardware supports both 16bit and 32bit swaps. Used for fbdev emulation
(probably 32bit swaps, but not fully sure). xorg radeon driver doesn't
use the byteswapping feature, because it is a PITA when bo's are moved
between vram and system memory.
R600+ supports bigendian framebuffer formats, so no byteswapping on
access is needed. Not sure whenever that includes 16bpp formats or
whenever this is limited to the 8 bit-per-color formats (simliar to
nvidia). Discussion focused on the pre-R600 hardware and how this
on-acpu-access byteswapping is more a problem than it helps ...
More information about the amd-gfx