On Sun, 28 Feb 2010 19:54:25 +0100 Antonio Ospite <ospite@xxxxxxxxxxxxxxxxx> wrote: > JF, the intent here is to cover all the range of values available in > Auto Exposure mode too, doesn't this make sense to you? > > I could set .maximum to 253 to limit the "UI" control precision but > then I should use 2*value when setting the registers in order to > cover the actual max value, this looks a little unclean. > > Anyhow, let me know what you prefer, I have no strong feelings on > that. If you want to save a byte, I'll agree. Looking at the rare chip documents I got, I often saw internal control values on 3 bytes (16 million values). Could anybody see the difference between values v and (v+1)? So, often, even when the internal controls are stored in only one byte, the ms-win drivers propose only ranges as 0..30 or 0..100. -- Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/ -- 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
