No. There are two mechanisms for configuring frame interval/rate as documented at https://www.kernel.org/doc/html/latest/ ... figuration. WIth libcamera you're interfacing directly with a raw sensor, hence 2.2.1 and V4L2_CID_HBLANK/V4L2_CID_VBLANK are applicable.So, my questions are:
[*]Should the VIDIOC_ENUM_FRAMEINTERVALS query be returning a valid value?
See above.[*]Does the VIDIOC_ENUM_FRAMEINTERVALS query work for others (ie: is this a hardware problem with two separate cameras? seems unlikely?)
Yes.[*]Is it reasonable for a library like FlashCap to make an assumption about supported frame intervals/rates if VIDIOC_ENUM_FRAMEINTERVALS does not return a valid value?
The bigger gotcha is going to be that you're looking at a raw sensor producing Bayer images, and configured using the Media Controller API. It's expected to be used through libcamera, not as a raw V4L2 device.[*]Is there some other gotcha with calling VIDIOC_ENUM_FRAMEINTERVALS that FlashCap is overlooking?
You may find that libcamerify (libcamera's V4L2 emulation layer) works for you app, but it just depends on exactly what the app needs to do.
Statistics: Posted by 6by9 — Sun Jan 21, 2024 8:14 am