Peter Pregler wrote: > way. Since we are talking about designing an API for the next 10 years > the question how to support such stuff in some way seems to be valid. > In other words, what is the v4l2-way to deal with hardware that has > dozens of non-standard options to control? Or is this out of scope? VIDIOC_QUERYCTRL + VIDIOC_G_CTRL + VIDIOC_S_CTRL with id >= V4L2_CID_PRIVATE_BASE Gerd -- Damn lot people confuse usability and eye-candy.
