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: DVB v3 API question
Date: Tue, 17 Feb 2009 21:36:33 +0100 [thread overview]
Message-ID: <499B1FD1.9080908@gmx.de> (raw)
In-Reply-To: <20090216222339.5ebad80d@pedra.chehab.org>
Mauro Carvalho Chehab wrote:
> On Mon, 16 Feb 2009 23:50:50 +0100
> Hans Verkuil <hverkuil@xs4all.nl> wrote:
>
>
>> Hi all,
>>
>> I've made a v4l-dvb tree containing the old DVB API sources as found here:
>> http://www.linuxtv.org/cgi-bin/viewcvs.cgi/DVB/doc/dvbapi/.
>>
>> This tree is here: http://www.linuxtv.org/hg/~hverkuil/v4l-dvb-api
>>
>
> It seems that we did suplicate work, except that, on your tree, you just
> dropped all CVS history.
>
> Anyway, the DVB API were just added to the repository with all the CVS history.
>
>
>> Run 'make spec' to build both the v4l2-spec and the dvb-spec, or
>> run 'make -C dvb-spec' to build only the latter. You'll need the transfig
>> package to get the dvb-spec to compile.
>>
>
> I didn't touch at the Makefiles. Feel free to submit this as a patch for the
> current tip.
>
>
>> My question is if this is indeed the most recent version that we have? There
>> is a dvb-api-v4 pdf document, but it is my understanding that v4 was
>> actually never implemented and never got beyond the proposal stage. Is that
>> correct? Or are there bits and pieces that were actually used?
>>
>
>
>> The original documentation for v4 is here:
>> http://www.linuxtv.org/cgi-bin/viewcvs.cgi/dvb-kernel-v4/linux/Documentation/dvb/
>>
>
> V4 is a proposal that were never finished.
>
> We're currently using V3 + S2API. This is named as V5.
>
> We need, of course, to update the docs to rename it to Version 5 and add S2API
> specs there. We should also review if the current DVB core and drivers match
> the V3. I suspect that maybe there are other changes that aren't applied yet at
> the docs.
>
>
Thanks Mauro and Hans for your fast help, its a good starting point for
updates.
The compiling requirements are not complete, missing are
- TransFig/fig2dev from xfig homepage
- dvipdf (where to find that btw..?)
The last one, dvipdf can be replaced by "dvipdfm", which is part of
teTex-3.0 which is anyway needed by only changing one line in Makefile:
dvbapi.pdf: dvbapi.dvi
- dvipdf $< $@
+ dvipdfm -o $@ $<
Regards,
Winfried
next prev parent reply other threads:[~2009-02-17 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 22:50 DVB v3 API question Hans Verkuil
2009-02-17 1:23 ` Mauro Carvalho Chehab
2009-02-17 20:36 ` wk [this message]
2009-02-17 21:04 ` 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=499B1FD1.9080908@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.