From: Jean Delvare <khali@linux-fr.org>
To: LMML <linux-media@vger.kernel.org>
Subject: Details about DVB frontend API
Date: Thu, 22 Oct 2009 21:13:30 +0200 [thread overview]
Message-ID: <20091022211330.6e84c6e7@hyperion.delvare> (raw)
Hi folks,
I am looking for details regarding the DVB frontend API. I've read
linux-dvb-api-1.0.0.pdf, it roughly explains what the FE_READ_BER,
FE_READ_SNR, FE_READ_SIGNAL_STRENGTH and FE_READ_UNCORRECTED_BLOCKS
commands return, however it does not give any information about how the
returned values should be interpreted (or, seen from the other end, how
the frontend kernel drivers should encode these values.) If there
documentation available that would explain this?
For example, the signal strength. All I know so far is that this is a
16-bit value. But then what? Do greater values represent stronger
signal or weaker signal? Are 0x0000 and 0xffff special values? Is the
returned value meaningful even when FE_HAS_SIGNAL is 0? When
FE_HAS_LOCK is 0? Is the scale linear, or do some values have
well-defined meanings, or is it arbitrary and each driver can have its
own scale? What are the typical use cases by user-space application for
this value?
That's the kind of details I'd like to know, not only for the signal
strength, but also for the SNR, BER and UB. Without this information,
it seems a little difficult to have consistent frontend drivers.
Thanks,
--
Jean Delvare
next reply other threads:[~2009-10-22 19:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 19:13 Jean Delvare [this message]
2009-10-22 19:27 ` Details about DVB frontend API Devin Heitmueller
2009-10-22 19:38 ` VDR User
2009-10-23 12:47 ` Jean Delvare
2009-10-22 20:10 ` Mauro Carvalho Chehab
2009-10-22 20:29 ` Manu Abraham
2009-10-23 0:12 ` Markus Rechberger
2009-10-23 1:00 ` Manu Abraham
2009-10-23 19:02 ` VDR User
2009-10-23 23:34 ` Markus Rechberger
2009-11-17 19:46 ` Mauro Carvalho Chehab
2009-11-17 19:55 ` Devin Heitmueller
2009-11-17 21:48 ` Jean Delvare
2009-11-17 22:53 ` Mauro Carvalho Chehab
2009-11-18 9:32 ` Devin Heitmueller
2009-11-18 14:04 ` Mauro Carvalho Chehab
2009-11-18 15:17 ` Devin Heitmueller
2009-11-18 15:35 ` Michael Krufky
2009-11-18 15:35 ` Devin Heitmueller
2009-11-20 9:29 ` Manu Abraham
2009-11-20 11:37 ` Julian Scheel
2009-11-20 16:08 ` Manu Abraham
2009-11-20 23:40 ` Julian Scheel
2009-12-04 20:02 ` VDR User
2009-12-04 20:59 ` Michael Krufky
2009-12-05 17:30 ` Mauro Carvalho Chehab
2009-12-05 17:42 ` Michael Krufky
2009-12-05 19:29 ` Mauro Carvalho Chehab
2009-12-07 21:00 ` Mauro Carvalho Chehab
2009-12-07 21:23 ` Mauro Carvalho Chehab
2009-10-23 12:53 ` Jean Delvare
2009-10-23 5:11 ` Mike Booth
2009-10-23 15:47 ` Jean Delvare
2009-10-23 16:45 ` Michael Krufky
2009-10-24 16:31 ` David T. L. Wong
-- strict thread matches above, loose matches on Subject: below --
2009-10-22 22:18 Hans Verkuil
2009-10-23 2:17 ` Steven Toth
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=20091022211330.6e84c6e7@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox