Conversation

Jarkko Sakkinen

For the v2 I think I have sane way to constrain the state i.e., in VCAM_IOC_CREATE:

__u32 nr_states;
__u32 states;

Each state (32 bytes per state) specifies configuration with pixel format, geometry, stride etc.

Obviously this means some redundancy perhaps because one has to address e.g. same width and height in different configurations but I think in the end this database approach is the most robust pick.
1
0
0
And I think I cap in the driver size states to 128 i.e. exactly 4KiB. It's like the driver definition blob sort of.
1
0
0
And despite perhaps a bit ugly/dirty approach this is also very macro and generator friendly way to go (e.g. with Rust I think this can be fluently supported via syntax tree macros).
0
0
0