From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: firedtv and removal of old IEEE1394 stack
Date: Wed, 9 Feb 2011 14:22:04 +0100 [thread overview]
Message-ID: <20110209142204.6eb445de@stein> (raw)
In-Reply-To: <4D5236E5.8060207@hoogenraad.net>
On Feb 09 Jan Hoogenraad wrote:
> For a problem description, and workaround, see:
>
> http://linuxtv.org/hg/~jhoogenraad/ubuntu-firedtv/
Do you mean
http://linuxtv.org/hg/~jhoogenraad/ubuntu-firedtv/rev/c8e14191e48d
"Disable FIREDTV for debian/ubuntu distributions with bad header files"?
I still don't see what the problem is. If you have a kernel without
drivers/ieee1394/*, then you also must have a kernel .config without
CONFIG_IEEE1394. Et voilà, firedtv builds fine (if CONFIG_FIREWIRE is y
or m). So, please make sure that .config and kernel sources match.
IOW the workaround c8e14191e48d addresses the wrong issue. Don't disable
CONFIG_DVB_FIREDTV; just make sure that the dependency of
CONFIG_DVB_FIREDTV_IEEE1394 on CONFIG_IEEE1394 is taken into account, like
in the mainline kernel's build system.
> and
>
> https://bugs.launchpad.net/ubuntu/+source/linux-kernel-headers/+bug/134222
Well, if you move arbitrary drivers/*/*.h files somewhere else where they
were never intended to be exported to, and supplant Kconfig by some
homegrewn ad hoc configuration builder, then you are of course on your own.
Still, my above comment on .config having to match the kernel sources
applies just as well and fully describes the problem and its solution. :-)
--
Stefan Richter
-=====-==-== --=- -=--=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-02-09 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 16:06 firedtv and removal of old IEEE1394 stack Hans Verkuil
2011-02-05 14:21 ` Stefan Richter
2011-02-05 14:32 ` Stefan Richter
2011-02-09 6:40 ` Jan Hoogenraad
2011-02-09 13:22 ` Stefan Richter [this message]
2011-02-09 14:24 ` Stefan Richter
2011-02-09 16:05 ` Mauro Carvalho Chehab
2011-02-09 15:51 ` Mauro Carvalho Chehab
2011-02-05 14:36 ` Hans Verkuil
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=20110209142204.6eb445de@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=hverkuil@xs4all.nl \
--cc=jan-conceptronic@hoogenraad.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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