From: wk <handygewinnspiel@gmx.de>
To: linux-media@vger.kernel.org
Subject: DVB-API v5 questions and no dvb developer answering ?
Date: Mon, 16 Feb 2009 18:48:13 +0100 [thread overview]
Message-ID: <4999A6DD.7030707@gmx.de> (raw)
The last week two guys were kindly asking here on the list where to find
a written DVB-API v5 documentation,
but nobody of the dvb driver community was answering.
http://www.mail-archive.com/linux-media@vger.kernel.org/msg01350.html
http://www.mail-archive.com/linux-media@vger.kernel.org/msg01300.html
Does that mean that:
- dvb developers are currently not interested in application developers
integrating new DVB-API v5? or..
- no dvb developer reading that list knows something about
documentation? or..
- does it simply not exist, so who is working on that api documentation
stuff?
The offical documentation found on linuxtv.org is outdated and already 5
years old, and describes only api v3.
See http://www.linuxtv.org/downloads/linux-dvb-api-1.0.0.pdf
Please read also the announcements on linuxtv:
http://www.linuxtv.org/news.php?entry=2008-09-23.mchehab
[quote]
Some improvements were proposed by the LinuxTV developers, in order to
improve the S2API, including:
...
* Update DVB API documentation to reflect the API changes;"
[/quote]
But also this statement is already now five months old,
so i guess documentation should be finished meanwhile or at least
started and usable/redistributable..
Is it possible to get some information on that topic?
-Winfried
next reply other threads:[~2009-02-16 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 17:48 wk [this message]
2009-02-16 18:08 ` DVB-API v5 questions and no dvb developer answering ? Hans Verkuil
2009-02-16 18:37 ` VDR User
2009-02-16 19:33 ` Devin Heitmueller
2009-02-16 20:51 ` VDR User
2009-02-16 21:39 ` wk
2009-02-16 22:01 ` Hans Verkuil
2009-02-17 0:43 ` Mauro Carvalho Chehab
2009-02-17 0:03 ` VDR User
2009-02-17 0:25 ` 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=4999A6DD.7030707@gmx.de \
--to=handygewinnspiel@gmx.de \
--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