From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.4] bttv and sparc64
Date: 07 Apr 2004 09:12:20 +0200 [thread overview]
Message-ID: <873c7gl0rv.fsf@bytesex.org> (raw)
In-Reply-To: pan.2004.04.06.23.39.42.565881@triplehelix.org
Joshua Kwan <joshk@triplehelix.org> writes:
> Many modules on sparc64 seem to require I2C support to
> compile correctly. Why do they not depend on CONFIG_I2C?
In my source tree bttv (correctly) depends on CONFIG_I2C_ALGOBIT ...
eskarina kraxel ~# grep BT848 /work/bk/2.4/linux-2.4.23/drivers/media/video/Config.in
dep_tristate ' BT848 Video For Linux' CONFIG_VIDEO_BT848 $CONFIG_VIDEO_DEV $CONFIG_PCI $CONFIG_I2C_ALGOBIT $CONFIG_SOUND
Gerd
--
http://bigendian.bytesex.org
next prev parent reply other threads:[~2004-04-07 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 23:39 [2.4] bttv and sparc64 Joshua Kwan
2004-04-07 7:12 ` Gerd Knorr [this message]
2004-04-07 23:52 ` Joshua Kwan
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=873c7gl0rv.fsf@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).