From: xof <xof@skynet.be>
To: linux-media@vger.kernel.org
Subject: Re: VL4-DVB compilation issue not covered by Daily Automated
Date: Wed, 13 Jan 2010 09:32:47 +0100 [thread overview]
Message-ID: <4B4D852F.4030506@skynet.be> (raw)
In-Reply-To: <829197381001121344l3ad94bdajdd4eb0345b895f2b@mail.gmail.com>
Devin Heitmueller a écrit :
> On Tue, Jan 12, 2010 at 4:26 PM, Hagen von Eitzen <hagen@von-eitzen.de> wrote:
>
>> Dear all,
>> as suggested by http://www.linuxtv.org/wiki/index.php/Bug_Report I report several warnings and errors not yet covered in latest http://www.xs4all.nl/~hverkuil/logs/Monday.log I get when compiling.
>> (The purpose of my experiments was trying to find out something about "0ccd:00a5 TerraTec Electronic GmbH")
>>
>> Regards
>> Hagen
>>
>
> This is an Ubuntu-specific issue (they improperly packaged their
> kernel headers), which will not be covered by the daily build system
> (which exercises various kernels but not across different Linux
> distribution versions).
>
> Devin
>
Are you sure? (it is an Ubuntu-only issue)
I can see several
> #include <asm/asm.h>
in the v4l tree that compile fine on Ubuntu
but only linux/drivers/media/dvb/firewire/firedtv-1394.c contains
> #include <asm.h>
and doesn't compile.
Unfortunately the asm.h asm/asm.h is not the only issue with
firedtv-1394.c (on Ubuntu/Karmic Koala?).
The /drivers/ieee1394/*.h seem to be in the linux-sources tree and not
in the linux-headers one (?)
Everywhere I look, I read "don't bother, just disable firedtv-1394.c"
until they fix it.
xof
---------------------
But my problem is 'I have no audio on an Hercules Smart TV 2 Stereo'
(bttv0: subsystem: 1540:952b; Card-100, Tuner-38).
It works on a Dapper LiveCD (with a good /etc/modprobe.d/bttv, a
~/.xawtv and xawtv installed).
The problem seems to exist since 2008...
next prev parent reply other threads:[~2010-01-13 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 21:26 VL4-DVB compilation issue not covered by Daily Automated Hagen von Eitzen
2010-01-12 21:44 ` Devin Heitmueller
2010-01-13 8:32 ` xof [this message]
2010-01-13 15:44 ` Devin Heitmueller
2010-01-14 17:27 ` xof
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=4B4D852F.4030506@skynet.be \
--to=xof@skynet.be \
--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