From: Jean Delvare <khali@linux-fr.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: LMML <linux-media@vger.kernel.org>
Subject: Re: Details about DVB frontend API
Date: Fri, 23 Oct 2009 14:53:48 +0200 [thread overview]
Message-ID: <20091023145348.33f0b1d8@hyperion.delvare> (raw)
In-Reply-To: <20091023051025.597c05f4@caramujo.chehab.org>
On Fri, 23 Oct 2009 05:10:25 +0900, Mauro Carvalho Chehab wrote:
> Em Thu, 22 Oct 2009 21:13:30 +0200
> Jean Delvare <khali@linux-fr.org> escreveu:
>
> > 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.
>
> We all want to know about that ;)
>
> Seriously, the lack of a description of the meaning of the ranges for those
> read values were already widely discussed at LMML and at the legacy dvb ML.
> We should return this discussion again and decide what would be the better
> way to describe those values.
>
> My suggestion is that someone summarize the proposals we had and give some time
> for people vote. After that, we just commit the most voted one, and commit the
> patches for it. A pending question that should also be discussed is what we will
> do with those dvb devices where we simply don't know what scale it uses. There
> are several of them.
>
> Btw, the new official documentation is the media infrastructure docbook that
> can be found at the Kernel and at:
> http://linuxtv.org/downloads/v4l-dvb-apis
>
> This covers both DVB and V4L API's.
Ah, thank you. So I was reading old documentation. Too bad that
googling for "linux dvb api" points to the old documents. Maybe the new
document needs some more keywords so that search engines index it
properly?
Also, on http://linuxtv.org/docs.php, I can see links to
http://linuxtv.org/downloads/linux-dvb-api-1.0.0.pdf for DVB and
http://www.linuxtv.org/downloads/video4linux/API/V4L2_API/spec-single/v4l2.html
for V4L... but no link to http://linuxtv.org/downloads/v4l-dvb-apis .
Shouldn't the links be updated?
--
Jean Delvare
next prev parent reply other threads:[~2009-10-23 12:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 19:13 Details about DVB frontend API Jean Delvare
2009-10-22 19:27 ` 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 [this message]
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=20091023145348.33f0b1d8@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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