From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [PATCH 00/15] DVB Frontend Documentation patches
Date: Tue, 7 Jun 2011 22:45:42 -0300 [thread overview]
Message-ID: <20110607224542.597d46bc@pedra> (raw)
This series of patches updates the DVB v5 documentation, sinchronizing
the current implementation with the API spec.
Among other things, it:
- adds a logic that discovers API gaps between the header
file and the API specs;
- adds/fixes the DVB S2API (DVBv5) additions;
- adds the FE_ATSC frontend descriptions (both v3 and v5);
- adds a relation of DVBv5 parameters for usage for each
supported delivery system.
The API updates were made at the best effort basis, by doing a sort
of "reverse engineering" approach, e. g., by looking at the code
and trying to figure out what changed, why and how. Due to that,
I bet people will find errors on it. Also, English is not my native
language, and I didn't have time for doing a language review.
so I'm sure that language/style/typo fixes are needed.
So, I'd like to encourage people to carefully read the docs and
send us patches with fixes.
Anyway, as the situation after those patches are better than before them,
I'm pushing it to the main repository. This helps to review, as the
linuxtv scripts will re-format the DocBook into html.
Mauro Carvalho Chehab (15):
[media] DocBook/Makefile: add references for several dvb structures
[media] DocBook/frontend.xml: Better document fe_type_t
[media] DocBook/frontend.xml: Link DVB S2API parameters
[media] DocBook/frontend.xml: Correlate dvb delivery systems
[media] DocBook/frontend.xml: add references for some missing info
[media] DocBook/frontend.xml: Better describe the frontend parameters
[media] DocBook/dvbproperty.xml: Document the remaining S2API parameters
[media] DocBook/dvbproperty.xml: Use links for all parameters
[media] DocBook/dvbproperty.xml: Reorganize the parameters
[media] DocBook/frontend.xml: Recomend the usage of the new API
[media] DocBook/dvbproperty.xml: Document the terrestrial delivery systems
[media] DocBook: Finish synchronizing the frontend API
[media] DocBook/dvbproperty.xml: Add Cable standards
[media] DocBook/dvbproperty.xml: Add ATSC standard
[media] DocBook/dvbproperty.xml: Add Satellite standards
Documentation/DocBook/media/Makefile | 17 +-
Documentation/DocBook/media/dvb/dvbproperty.xml | 965 +++++++++++++++--------
Documentation/DocBook/media/dvb/frontend.xml | 285 +++++---
3 files changed, 833 insertions(+), 434 deletions(-)
next reply other threads:[~2011-06-08 1:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 1:45 Mauro Carvalho Chehab [this message]
2011-06-08 2:10 ` [PATCH 16/15] [media] DocBook/dvbproperty.xml: Better name the ISDB-T layers Mauro Carvalho Chehab
2011-06-08 2:20 ` [PATCH 00/15] DVB Frontend Documentation patches Mauro Carvalho Chehab
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=20110607224542.597d46bc@pedra \
--to=mchehab@redhat.com \
--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