[lkml]   [2017]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.
On Fri, Apr 21, 2017 at 11:38:28AM +0200, Gerd Hoffmann wrote:
> Hi,
> > > 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.

Eh? Everything that is affected by byte order has the relevant comments.
If they don't, then that's a bug.

> 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.

The "standard" is fourcc. Whether there is any official reference for
that is unclear. That's exactly why I added the explicit comments into
drm_fourcc.h so that people don't have to go trawling the internets
looking for information on what each pixel format might mean.

Ville Syrjälä
Intel OTC

 \ /
  Last update: 2017-04-21 11:45    [W:0.061 / U:7.928 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site