[PATCH] drm: fourcc byteorder: brings header file comments in line with reality.
kraxel at redhat.com
Fri Apr 21 09:38:28 UTC 2017
> > Leaving the yuv formats as-is. I have no idea if and how those are used
> > on bigendian machines.
> just an idea - since we are not sure how the remaining formats are being
> used, should those be marked somehow uncertain whether they are little
> or native endian?
ATM the yuv don't have any byte order annotations, and I simply left
them that way. So it is as clear/unclear as before.
IIRC someone mentioned that for the yuv fourccs there actually is some
standard about the exact ordering. Anyone has a good reference? We
could stick a link to it into a comment.
More information about the dri-devel