<really big snip>
So, what do these two deep questions, which confound the assembled
wisdom of an entire list of Linux video developers, have to do with
tables in userspace? None that I can see, unless someone wants to
provide a mechanism for the information, having been collected in the
module, to be available to the table in userspace.
I'm not saying that userspace tables would solve all problems. I'm just
saying that this should be part of the solution.
For sure we need to have a way for retrieving this information for
devices like the sq905 cameras, where the information can't be currently
be determined by userspace.
In the case of sq905, this information is static, right? If so, IMO, the
better approach is to use a flag at the v4l2_input, as already discussed
in this thread.
Yes we all seem to agree on this. Adam, since you started this thread can you
write a small RFC with that solution worked out with proposed videodev2.h changes?
Note that I'm only talking about input flags for the orientation problem and
not the pivotting problem. I think the pivotting problem may need some more
discussion. But since we all seem to be in agreement wrt to orientation problem
and specifically the sq905 problem, lets do one more RFC, then everyone does a
+1 to that and we move forward with this as a solution for the orientation problem.
Regards,
Hans
p.s.
For the pivotting problem I'm tending towards a special control class which
contains read-only controls which are really camera properties. This will allow
us to cope with any granularity of pivoting sensors. This could then also be
used for in example aperture. But lets start a new thread for that.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
