From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: firedtv and removal of old IEEE1394 stack
Date: Sat, 5 Feb 2011 15:21:22 +0100 [thread overview]
Message-ID: <20110205152122.3b566ef0@stein> (raw)
In-Reply-To: <201102031706.12714.hverkuil@xs4all.nl>
On Feb 03 Hans Verkuil wrote:
> Hi Stefan,
>
> I discovered (somewhat to my surprise) that the IEEE1394 stack was removed
> from the kernel in 2.6.37. Your commit 66fa12c571d35e3cd62574c65f1785a460105397
> indicates that the ieee1394 firedtv code can be removed in an indepedent commit.
>
> It seems that this was forgotten since the firedtv-1394.c source is still
> present.
It is not forgotten, just delayed. :-)
> Is it OK if I remove it? I assume that anything that depends on DVB_FIREDTV_IEEE1394
> can be deleted.
This stuff can be removed indeed, and will be. After that, some further
simplifications are possible since the backend abstraction is no longer
necessary.
> It would be nice to remove this since building the firedtv driver for older kernels
> always gives problems on ubuntu due to some missing ieee1394 headers.
How so? Then there is something wrong with the backported sources. If
CONFIG_IEEE1394 is not defined, neither make nor gcc ever see anything
that includes ieee1394 headers. Vice versa regarding CONFIG_FIREWIRE and
the newer firewire headers.
--
Stefan Richter
-=====-==-== --=- --=-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2011-02-05 14:21 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 [this message]
2011-02-05 14:32 ` Stefan Richter
2011-02-09 6:40 ` Jan Hoogenraad
2011-02-09 13:22 ` Stefan Richter
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=20110205152122.3b566ef0@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=hverkuil@xs4all.nl \
--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 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.