On Fri, Mar 13, 2009 at 5:32 PM, Devin Heitmueller <devin.heitmueller@xxxxxxxxx> wrote: > On Fri, Mar 13, 2009 at 5:11 PM, Trent Piepho <xyzzy@xxxxxxxxxxxxx> wrote: >> I like 8.8 fixed point a lot better. It gives more precision. The range >> is more in line with that the range of real SNRs are. Computers are >> binary, so the math can end up faster. It's easier to read when printed >> out in hex, since you can get the integer part of SNR just by looking at >> the first byte. E.g., 25.3 would be 0x194C, 0x19 = 25 db, 0x4c = a little >> more than quarter. Several drivers already use it. > > Wow, I know you said you like that idea alot better, but I read it and > it made me feel sick to my stomach. Once we have a uniform format, we > won't need to show it in hex at all. Tools like femon and scan can > just show the value in decimal (they show it in hex because it's > definition varies by device). > > Target applications can reformat the value any way you prefer. This > is a kernel interface. > > On a separate note, do you know specifically which drivers use that > format? I was putting together a table of all the various > demodulators and which format they use, so if you have demods you know > about I would be interested in filling out that data. LGDT330X, for both the 3302 and 3303 (although the 3302 work was a guess -- its probably close enough) ...and both of the OREN demod drivers. -Mike -- 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
