From: wk <handygewinnspiel@gmx.de>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: VDR User <user.vdr@gmail.com>, Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org
Subject: Re: DVB-API v5 questions and no dvb developer answering ?
Date: Mon, 16 Feb 2009 22:39:44 +0100 [thread overview]
Message-ID: <4999DD20.5080801@gmx.de> (raw)
In-Reply-To: <412bdbff0902161133u22febbc7v9ca9173bb547bb99@mail.gmail.com>
Devin Heitmueller wrote:
> As always we continue to welcome patches, including for the
> documentation. Instead of bitching and moaning, how about you roll up
> your sleeves and actually help out?
>
> Let's try to remember that pretty much all the developers here are
> volunteers, so berating them for not doing things fast enough for your
> personal taste is not really very productive.
>
> Regards,
>
> Devin
>
>
Devin,
can you please explain, how others should contribute to an dvb api if
- the only DVB API file to be found is a pdf file, and therefore not
editable. Which files exactly to be edited you are writing of?
- one doesn't know which ioctls exist for what function, which return
codes and arguments, how to understand and to use..?
What you suggest is almost impossible to someone not perfectly familiar
with the drivers, only for dvb experts who have written at least a bunch
of drivers.
Its something different than sending patches for one single driver where
some bug/improvement was found.
On the other hand, in principle a driver without existing api doc is
useless. Nobody can use it, the same for drivers with undocumented new
features.
Regards,
Winfried
next prev parent reply other threads:[~2009-02-16 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 17:48 DVB-API v5 questions and no dvb developer answering ? wk
2009-02-16 18:08 ` 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 [this message]
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=4999DD20.5080801@gmx.de \
--to=handygewinnspiel@gmx.de \
--cc=devin.heitmueller@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=user.vdr@gmail.com \
/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