Re: [linux-media] API V3 vs SAPI behavior difference in reading tuning parameters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/19/2011 06:03 PM, Thierry LELEGARD wrote:
> OK, then what? Is the S2API behavior (returning cached - but incorrect - tuning
> parameter values) satisfactory for everyone or shall we adapt S2API to mimic the
> API V3 behavior (return the actual tuning parameter values as automatically
> adjusted by the driver)?

To quote myself:

if that's still the case in Git (I didn't verify), then it should indeed
be changed to behave like v3 does. Would you mind to submit a patch, please?

I haven't heard any objections, so just go on if you want. Otherwise I
might prepare a patch once time permits.

Regards,
Andreas
--
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux