On Fri, Jan 14, 2011 at 8:35 AM, Thierry LELEGARD <tlelegard@xxxxxxxxxxxx> wrote: > But there is worse. If I set a wrong parameter in the tuning operation, > for instance guard interval 1/32, the API V3 returns the correct value > which is actually used by the tuner (GUARD_INTERVAL_1_8), while S2API > returns the "cached" value which was set while tuning (GUARD_INTERVAL_1_32). This is actually a bad thing. If you specify the wrong parameter and it still works, then that can lead to all sort of misleading behavior. For example, imagine the next person who submits scan results based on using such a driver. It works for him because his driver lied, but the resulting file works for nobody else. If you specify an explicit value incorrectly (not auto) and it still works, that is a driver bug which should be fixed. Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
