From: Christoph Hellwig <hch@infradead.org>
To: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: tighten i2c dependancies
Date: Sat, 30 Apr 2005 08:35:18 +0100 [thread overview]
Message-ID: <20050430073518.GB22673@infradead.org> (raw)
In-Reply-To: <20050430055745.GB832@redhat.com>
On Sat, Apr 30, 2005 at 01:57:45AM -0400, Dave Jones wrote:
> config I2C_ALI15X3
> tristate "ALI 15x3"
> - depends on I2C && PCI && EXPERIMENTAL
> + depends on X86 && I2C && PCI && EXPERIMENTAL
> help
> If you say yes to this option, support will be included for the
> Acer Labs Inc. (ALI) M1514 and M1543 motherboard I2C interfaces.
one of the ali bridges is used on sparc64 aswell, not sure which one.
> @@ -41,7 +41,7 @@ config I2C_ALI15X3
>
> config I2C_AMD756
> tristate "AMD 756/766/768/8111 and nVidia nForce"
> - depends on I2C && PCI && EXPERIMENTAL
> + depends on X86 && I2C && PCI && EXPERIMENTAL
> help
> If you say yes to this option, support will be included for the AMD
> 756/766/768 mainboard I2C interfaces. The driver also includes
also used on alpha and ppc64
> config I2C_AMD8111
> tristate "AMD 8111"
> - depends on I2C && PCI && EXPERIMENTAL
> + depends on X86 && I2C && PCI && EXPERIMENTAL
> help
> If you say yes to this option, support will be included for the
> second (SMBus 2.0) AMD 8111 mainboard I2C interface.
ppc64
> config I2C_PIIX4
> tristate "Intel PIIX4"
> - depends on I2C && PCI
> + depends on X86 && I2C && PCI
> help
> If you say yes to this option, support will be included for the Intel
> PIIX4 family of mainboard I2C interfaces. Specifically, the following
> @@ -437,7 +437,7 @@ config I2C_STUB
the PIIX is used on various non-x86 systems, at least ppc and mips come to
mind.
next prev parent reply other threads:[~2005-04-30 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 5:57 tighten i2c dependancies Dave Jones
2005-04-30 7:35 ` Christoph Hellwig [this message]
2005-04-30 7:42 ` Geert Uytterhoeven
2005-04-30 11:06 ` Christer Weinigel
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=20050430073518.GB22673@infradead.org \
--to=hch@infradead.org \
--cc=davej@redhat.com \
--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 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.