From: Anssi Hannula <anssi.hannula@gmail.com>
To: Thierry Lelegard <thierry.lelegard@tv-numeric.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Interpretation of FE_READ_BER
Date: Mon, 31 Mar 2008 02:27:39 +0300 [thread overview]
Message-ID: <47F021EB.6010104@gmail.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAJf2pBr8u1U+Z+cArRcz8PMKAAAAQAAAASuTAGpqJw0asMd7tD3VNFwEAAAAA@tv-numeric.com>
Thierry Lelegard wrote:
> Hi,
Hi! I'm not an expert in this matter, but it seems no one else is replying.
> What is the interpretation of the value returned by ioctl FE_READ_BER?
AFAIK the exact meaning of all the values is driver/device-specific.
> Normally, a bit-error-rate is something like 10^-6 (typically not an
> integer value).
>
> There is no clue in the Linux DVB API doc. Google reports similar
> questions but none with an answer. I have just seen one note suggesting
> it could be a multiple of 10^-9. Looks good to me but since there is
> no good definition of this parameter in the docs, I wonder if drivers
> implement them in a consistent way.
I don't think so.
> With my Nova-T 500 (Fedora 8, kernel 2.6.24.3-12, recent v4l hg tree),
> the reception is quite fine, FE_READ_SIGNAL_STRENGTH returns 40000 (60%),
> but FE_READ_BER always returns 0. Does this mean "not even the slightest
> error" (to good to be true), "not supported" (should return errno ENOSYS),
> "driver bug"?
0 can very well mean there is no errors, it is not that uncommon (I've
seen it with my devices in good conditions).
--
Anssi Hannula
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-03-30 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 10:49 [linux-dvb] Interpretation of FE_READ_BER Thierry Lelegard
2008-03-30 23:27 ` Anssi Hannula [this message]
2008-04-08 20:12 ` Morgan Tørvolt
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=47F021EB.6010104@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=thierry.lelegard@tv-numeric.com \
/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.