From: wk <handygewinnspiel@gmx.de>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Subject: Re: V4L2 spec
Date: Mon, 09 Mar 2009 23:03:28 +0100 [thread overview]
Message-ID: <49B59230.1090305@gmx.de> (raw)
In-Reply-To: <alpine.LRH.2.00.0903090803010.6607@caramujo.chehab.org>
>
> I think so. The better would be to convert DVB api to docbook (as used
> by all other kernel documents), and add a developers document for the
> kernel API for both at the kernel documentation structure).
>
> However, this is a huge task that someone should volunteer for doing,
> otherwise, it won't happen.
>
> Cheers,
> Mauro
>
Sorry Mauro,
but i disagree with you.
Its a bad idea to expect someone else, the magic volunteer, doing work
with *deep impact* on the dvb driver API structure or documentation.
Working on this topic determines complete usability of the driver, so
MAIN DEVELOPERS have to REVIEW and CONTRIBUTE.
If they think, that they cannot do such work in parallel, they should to
stop work on drivers for some time.
Status from application side of view at the moment: *not usable* without
re-inventing the wheel.
The very same with the structures in frontend.h, a lot of things are not
understandable. I give you some examples (i could give more...):
- TRANSMISSION_MODE_4K is missing, but still mentioned in 300468
v.1.9.1 "6.2.13.4 Terrestrial delivery system descriptor"
- the same for BANDWIDTH_5_MHZ, also 300468 v.1.9.1 "6.2.13.4
Terrestrial delivery system descriptor"
- POLARIZATION for QPSK frontends is nowhere defined in frontend.h at
all, forcing applications to do its own definitions,
"6.2.13.2 Satellite delivery system descriptor" gives clear
definitions - so why are they not defined in frontend.h?
- ATSC frontends are mixed cable and terrestrian, whereas older DVB-C
and DVB-T are *strictly* separated
- struct dvb_qpsk_parameters is missing (at least!) to be usable again
* fe_modulation_t
* fe_pilot_t
* fe_rolloff_t
* fe_delivery_system_t
* west_east_flag
* scrambling_sequence_selector
* multiple_input_stream_flag
- nearly the same for dvb_qam_parameters, dvb_ofdm_parameters,
dvb_atsc_parameters..., at least delivery_system needs to be here
Working on documentation would fix *all* of this problems.
Regards,
Winfried
next prev parent reply other threads:[~2009-03-09 22:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 14:23 V4L2 spec Hans Verkuil
2009-03-06 16:20 ` wk
2009-03-09 11:08 ` Mauro Carvalho Chehab
2009-03-09 19:47 ` Hans Verkuil
2009-03-10 18:39 ` Trent Piepho
2009-03-09 22:03 ` wk [this message]
2009-03-09 22:10 ` Devin Heitmueller
2009-03-09 22:44 ` Hans Verkuil
2009-03-09 23:46 ` Andy Walls
2009-03-09 23:56 ` Andy Walls
2009-03-10 0:36 ` Mauro Carvalho Chehab
2009-03-10 0:54 ` Mauro Carvalho Chehab
2009-03-10 7:14 ` Hans Verkuil
2009-03-10 17:18 ` wk
2009-03-09 22:55 ` Mauro Carvalho Chehab
2009-03-10 16:45 ` wk
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=49B59230.1090305@gmx.de \
--to=handygewinnspiel@gmx.de \
--cc=hverkuil@xs4all.nl \
--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;
as well as URLs for NNTP newsgroup(s).