>> modulation type (or advanced tuner) that we know of today.
>> how generic types are passed to/from the kernel.
> avoids the ugly transaction stuff and keeps it atomic.
future hardware require radically different parameters/operations.
Hence, this API supports both mechanisms.
> - need for .val being variable lenght or a union of different types?
> - extend existing enums or define new ones for MODULATION etc?
modulation types, FECs etc. In more cases than not, this is the case.
compatibility for existing users. No ABI changes.
direction that's being taken so far is sound, then I'll look into this next.
to query some basic tuner metrics (locked/sync etc).
do not want to migrate overnight. That's an unwritten goal.
to return a superset of data in a cleaner non-fixed-structured way.
> or which one they think will be ready for prime time sooner.
> more flexible, but who knows how much work it'll take to complete.
Lastly, a few things I want to mention.
handle the ioctl. No changes have been made to the frontend drivers.
only had 6-8 hours work of engineering behind it. It's proof of concept.
working, and demonstrate many of the userland signal/statistic API's.
flush out more code this would probably lead to an RFC for your approval.