From: Steven Toth <stoth@linuxtv.org>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: Andy Walls <awalls@radix.net>,
linux-media@vger.kernel.org, Trent Piepho <xyzzy@speakeasy.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Ang Way Chuang <wcang@nav6.org>, VDR User <user.vdr@gmail.com>,
Manu Abraham <abraham.manu@gmail.com>
Subject: Re: The right way to interpret the content of SNR, signal strength and BER from HVR 4000 Lite
Date: Tue, 24 Mar 2009 18:08:03 -0400 [thread overview]
Message-ID: <49C959C3.3060402@linuxtv.org> (raw)
In-Reply-To: <412bdbff0903241439u472be49mbc2588abfc1d675d@mail.gmail.com>
>> Let me ask this rhetorical question: if we did nothing more than just
>> normalize the SNR to provide a consistent value in dB, and did nothing
>> more than normalize the existing strength field to be 0-100%, leaving
>> it up to the driver author to decide the actual heuristic, what
>> percentage of user's needs would be fulfilled?
We don't need a new API and more complexity and/or code confusion, just
standardize on the unit values for the existing APIs.
1) SNR in either units of db or units of .1 db (I don't care which, although I
prefer the later).
2) Strength as a percentage.
The approach Devin outlined above has my support.
- Steve
next prev parent reply other threads:[~2009-03-24 22:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 1:53 The right way to interpret the content of SNR, signal strength and BER from HVR 4000 Lite Ang Way Chuang
2009-03-13 2:23 ` VDR User
2009-03-13 4:19 ` Ang Way Chuang
2009-03-13 14:27 ` Devin Heitmueller
2009-03-13 21:11 ` Trent Piepho
2009-03-13 21:32 ` Devin Heitmueller
2009-03-13 21:52 ` Michael Krufky
2009-03-13 22:27 ` VDR User
2009-03-13 22:31 ` Devin Heitmueller
2009-03-15 13:20 ` wk
2009-03-15 14:40 ` Devin Heitmueller
2009-03-13 23:55 ` Trent Piepho
2009-03-19 13:16 ` Mauro Carvalho Chehab
2009-03-19 20:11 ` Trent Piepho
2009-03-19 22:17 ` Trent Piepho
2009-03-19 22:36 ` Devin Heitmueller
2009-03-19 23:06 ` Trent Piepho
2009-03-20 14:21 ` Devin Heitmueller
2009-03-20 19:38 ` Trent Piepho
2009-03-19 23:27 ` Manu Abraham
2009-03-20 6:55 ` Manu Abraham
2009-03-20 13:07 ` Devin Heitmueller
2009-03-20 15:07 ` VDR User
2009-03-27 9:14 ` Roberto Ragusa
2009-03-22 2:45 ` Andy Walls
2009-03-22 10:27 ` Manu Abraham
2009-03-23 1:00 ` Devin Heitmueller
2009-03-24 21:39 ` Devin Heitmueller
2009-03-24 22:08 ` Steven Toth [this message]
2009-03-25 1:12 ` Andy Walls
2009-03-24 23:18 ` Manu Abraham
2009-03-24 23:28 ` Mika Laitio
2009-03-24 23:46 ` Manu Abraham
2009-03-25 0:29 ` VDR User
2009-03-25 14:38 ` Devin Heitmueller
2009-03-25 22:02 ` Manu Abraham
2009-03-25 22:27 ` Devin Heitmueller
2009-03-27 18:09 ` Devin Heitmueller
2009-03-27 19:00 ` Manu Abraham
2009-03-24 23:54 ` Manu Abraham
2009-03-14 0:43 ` Andy Walls
2009-03-14 1:34 ` Trent Piepho
2009-03-14 2:44 ` Andy Walls
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C959C3.3060402@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=abraham.manu@gmail.com \
--cc=awalls@radix.net \
--cc=devin.heitmueller@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=user.vdr@gmail.com \
--cc=wcang@nav6.org \
--cc=xyzzy@speakeasy.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.