12/20/2023 0 Comments H264_omxdev/video14 is the high res output which can be in any of these formats : 'Y14P' (14-bit Greyscale (MIPI Packed)) : 'Y12P' (12-bit Greyscale (MIPI Packed)) : 'Y10P' (10-bit Greyscale (MIPI Packed)) Which can also be produced graphically by usingĬode: Select all $ v4l2-ctl -list-formats-out -d 13 Run "media-ctl -p -d /dev/media2" on a Pi and you'll getĬode: Select all Media controller API version 5.10.17 Media Controller is the API for enumerating what device nodes link to what. V4L2 also only allows one CAPTURE and one OUTPUT queue per device node, so to support 1 input and 3 outputs (high res, low res, and stats) you have to have 4 device nodes. When considering a memory to memory device such as a codec or ISP those terms are still applied, so you pass frames in on the V4L2_BUF_TYPE_VIDEO_OUTPUT queue, and get the output on the V4L2_BUF_TYPE_VIDEO_CAPTURE queue. So a CAPTURE device produces (outputs) frames, and an OUTPUT device accepts (input) frames. Originally it had webcams as CAPTURE devices, and video overlay devices as OUTPUT devices. V4L2 has a big annoyance in terminology due to history. It's more than happy to take Bayer in and spit RGB (or YUV) out. convert raw to rgb) unless I'm missing something. That's interesting, but the userland interface of the V4L2 ISP doesn't seem to support handing it a buffer for it to process (e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |