From: Andreas Oberritter <obi@linuxtv.org>
To: Luca Olivetti <luca@ventoso.org>
Cc: linux-media Mailing List <linux-media@vger.kernel.org>
Subject: Re: femon signal strength
Date: Mon, 07 Nov 2011 20:16:40 +0100 [thread overview]
Message-ID: <4EB82E98.9030105@linuxtv.org> (raw)
In-Reply-To: <4EB7F57E.4060303@ventoso.org>
On 07.11.2011 16:13, Luca Olivetti wrote:
> Al 07/11/2011 11:47, En/na Andreas Oberritter ha escrit:
>> I didn't receive Devin's mail, so I'm replying to this one instead, see
>> below:
>
> [...]
>> Quoting myself from three years ago, I propose to add an interface to
>> read SNR in units of db/100:
>
> A previous version of the dvb api specified the unit of snr as db/1000000
>
> http://linuxtv.org/downloads/legacy/old/linux_dvb_api-20020304.pdf
>
> page 55, FE_READ_SIGNAL_STRENGTH
>
> "The signal-to-noise ratio, as a multiple of 10E-6 dB, is stored into *snr.
> Example: a value of 12,300,000 corresponds to a signal-
> to-noise ratio of 12.3 dB."
>
> It also defined the unit for ber (multiple of 10E-9).
>
> However it was dropped from subsequent revisions, I don't know why.
>
> Bye
It was dropped because most (or all?) of the drivers available at the
time were created without access to register descriptions and thus
nobody of the developers knew how to calculate meaningful values and/or
nobody was allowed to publish code based on confidential information. It
was decided that big values meant good signal instead, which was good
enough to print a signal meter bar without any real numbers.
The situation has changed since then. I think two decimal digits should
be sufficient. A value displayed to the user would probably have at most
one decimal digit. The SNR measured by a demodulator isn't very
accurate, so adding more decimal digits doesn't improve the precision.
Personally, I don't care much whether the unit is db/10, db/100 or
db/1000. I just think db/100 is a reasonable choice and IIRC it's the
unit that most of the vendor drivers I've seen in the past are using.
Regards,
Andreas
prev parent reply other threads:[~2011-11-07 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 4:36 femon signal strength James
2011-10-26 8:15 ` Devin Heitmueller
2011-10-26 19:45 ` James
2011-10-26 19:49 ` Devin Heitmueller
2011-10-26 19:58 ` James
2011-11-05 10:10 ` Steffen Barszus
[not found] ` <CAGoCfiwC+7pkY6ZchySBYRkyY1XjFjKeJYQEPTc2ZiBN-pdoyw@mail.gmail.com>
2011-11-06 13:15 ` Steffen Barszus
[not found] ` <CAGoCfixoOwZumohwJrLVKhfpUNGYwbD9uSq7nM0GhqriOx0FxA@mail.gmail.com>
2011-11-06 19:59 ` Steffen Barszus
2011-11-07 10:47 ` Andreas Oberritter
2011-11-07 15:13 ` Luca Olivetti
2011-11-07 19:16 ` Andreas Oberritter [this message]
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=4EB82E98.9030105@linuxtv.org \
--to=obi@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=luca@ventoso.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.