2.14. Reserved Format Identifiers¶
These formats are not defined by this specification, they are just
listed for reference and to avoid naming conflicts. If you want to
register your own format, send an e-mail to the linux-media mailing list
https://linuxtv.org/lists.php
for inclusion in the videodev2.h file. If you want to share your
format with other developers add a link to your documentation and send a
copy to the linux-media mailing list for inclusion in this section. If
you think your format should be listed in a standard format section
please make a proposal on the linux-media mailing list.
Identifier |
Code |
Details |
|---|---|---|
|
‘dvsd’ |
unknown |
|
‘E625’ |
Compressed format of the ET61X251 driver. |
|
‘HI24’ |
8 bit RGB format used by the BTTV driver. |
|
‘CPIA’ |
YUV format used by the gspca cpia1 driver. |
|
‘JPGL’ |
JPEG-Light format (Pegasus Lossless JPEG) used in Divio webcams NW 80x. |
|
‘S501’ |
YUYV per line used by the gspca driver. |
|
‘S505’ |
YYUV per line used by the gspca driver. |
|
‘S508’ |
YUVY per line used by the gspca driver. |
|
‘S561’ |
Compressed GBRG Bayer format used by the gspca driver. |
|
‘P207’ |
Compressed BGGR Bayer format used by the gspca driver. |
|
‘M310’ |
Compressed BGGR Bayer format used by the gspca driver. |
|
‘JL20’ |
JPEG compressed RGGB Bayer format used by the gspca driver. |
|
‘O511’ |
OV511 JPEG format used by the gspca driver. |
|
‘O518’ |
OV518 JPEG format used by the gspca driver. |
|
‘PJPG’ |
Pixart 73xx JPEG format used by the gspca driver. |
|
‘S401’ |
Compressed RGB format used by the gspca se401 driver |
|
‘905C’ |
Compressed RGGB bayer format used by the gspca driver. |
|
‘MJPG’ |
Compressed format used by the Zoran driver |
|
‘PWC1’ |
Compressed format of the PWC driver. |
|
‘PWC2’ |
Compressed format of the PWC driver. |
|
‘S910’ |
Compressed format of the SN9C102 driver. |
|
‘S920’ |
YUV 4:2:0 format of the gspca sn9c20x driver. |
|
‘SONX’ |
Compressed GBRG bayer format of the gspca sn9c2028 driver. |
|
‘S680’ |
Bayer format of the gspca stv0680 driver. |
|
‘WNVA’ |
Used by the Winnov Videum driver, http://www.thedirks.org/winnov/ |
|
‘TM60’ |
Used by Trident tm6000 |
|
‘CITV’ |
Used by xirlink CIT, found at IBM webcams. Uses one line of Y then 1 line of VYUY |
|
‘KONI’ |
Used by Konica webcams. YUV420 planar in blocks of 256 pixels. |
|
‘YYUV’ |
unknown |
|
‘Y04 ‘ |
Old 4-bit greyscale format. Only the most significant 4 bits of each byte are used, the other bits are set to 0. |
|
‘Y06 ‘ |
Old 6-bit greyscale format. Only the most significant 6 bits of each byte are used, the other bits are set to 0. |
|
‘S5CI’ |
Two-planar format used by Samsung S5C73MX cameras. The first plane contains interleaved JPEG and UYVY image data, followed by meta data in form of an array of offsets to the UYVY data blocks. The actual pointer array follows immediately the interleaved JPEG/UYVY data, the number of entries in this array equals the height of the UYVY image. Each entry is a 4-byte unsigned integer in big endian order and it’s an offset to a single pixel line of the UYVY image. The first plane can start either with JPEG or UYVY data chunk. The size of a single UYVY block equals the UYVY image’s width multiplied by 2. The size of a JPEG chunk depends on the image and can vary with each line. The second plane, at an offset of 4084 bytes, contains a 4-byte offset to the pointer array in the first plane. This offset is followed by a 4-byte value indicating size of the pointer array. All numbers in the second plane are also in big endian order. Remaining data in the second plane is undefined. The information in the second plane allows to easily find location of the pointer array, which can be different for each frame. The size of the pointer array is constant for given UYVY image height. In order to extract UYVY and JPEG frames an application can initially set a data pointer to the start of first plane and then add an offset from the first entry of the pointers table. Such a pointer indicates start of an UYVY image pixel line. Whole UYVY line can be copied to a separate buffer. These steps should be repeated for each line, i.e. the number of entries in the pointer array. Anything what’s in between the UYVY lines is JPEG data and should be concatenated to form the JPEG stream. |
|
‘MT21’ |
Compressed two-planar YVU420 format used by Mediatek MT8173, MT8192,
MT8195 and more. The compression is lossless. This format have
similitude with |
|
‘QC08C’ |
Compressed Macro-tile 8-Bit YUV420 format used by Qualcomm platforms. It is an opaque intermediate format. The used compression is lossless and it is used by various multimedia hardware blocks like GPU, display controllers, ISP and video accelerators. It contains four planes for progressive video and eight planes for interlaced video. |
|
‘QC10C’ |
Compressed Macro-tile 10-Bit YUV420 format used by Qualcomm platforms. It is an opaque intermediate format. The used compression is lossless and it is used by various multimedia hardware blocks like GPU, display controllers, ISP and video accelerators. It contains four planes for progressive video. |
|
‘AJPG’ |
ASPEED JPEG format used by the aspeed-video driver on Aspeed platforms, which is generally adapted for remote KVM. On each frame compression, I will compare the new frame with previous one to decide which macroblock’s data is changed, and only the changed macroblocks will be compressed. The implementation is based on AST2600 A3 datasheet, revision 0.9, which is not publicly available. Or you can reference Video stream data format – ASPEED mode compression of SDK_User_Guide which available on github. Decoder’s implementation can be found here, aspeed_codec |
|
‘MT2110T’ |
This format is two-planar 10-Bit tile mode and having similitude with
|
|
‘MT2110R’ |
This format is two-planar 10-Bit raster mode and having similitude with
|
|
‘HXTL’ |
Compressed format used by Nuvoton NPCM video driver. This format is defined in Remote Framebuffer Protocol (RFC 6143, chapter 7.7.4 Hextile Encoding). |