summaryrefslogtreecommitdiffstats
path: root/lib/crc-t10dif.c
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2011-11-17 18:05:13 +0200
committerDave Airlie <airlied@redhat.com>2011-12-01 14:16:10 +0000
commit04b3924db60f974d2b4af0b2e19a0ae7ca202dc7 (patch)
treef16a79ad676ba2333ee5af9c431b9882d574af9e /lib/crc-t10dif.c
parent248dbc2350501e2c7b9f5ceb60c75515d82f4134 (diff)
downloadblackbird-op-linux-04b3924db60f974d2b4af0b2e19a0ae7ca202dc7.tar.gz
blackbird-op-linux-04b3924db60f974d2b4af0b2e19a0ae7ca202dc7.zip
drm: Redefine pixel formats
Name the formats as DRM_FORMAT_X instead of DRM_FOURCC_X. Use consistent names, especially for the RGB formats. Component order and byte order are now strictly specified for each format. The RGB format naming follows a convention where the components names and sizes are listed from left to right, matching the order within a single pixel from most significant bit to least significant bit. The YUV format names vary more. For the 4:2:2 packed formats and 2 plane formats use the fourcc. For the three plane formats the name includes the plane order and subsampling information using the standard subsampling notation. Some of those also happen to match the official fourcc definition. The fourccs for for all the RGB formats and some of the YUV formats I invented myself. The idea was that looking at just the fourcc you get some idea what the format is about without having to decode it using some external reference. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'lib/crc-t10dif.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud