From: Jean Delvare <khali@linux-fr.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>,
i2c@lm-sensors.org, Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [PATCH 2/2] i2c-ibm_iic driver
Date: Wed, 20 Feb 2008 07:57:31 +0100 [thread overview]
Message-ID: <20080220075731.7675bbbb@hyperion.delvare> (raw)
In-Reply-To: <200802192355.17707.arnd@arndb.de>
Hi Arnd,
On Tue, 19 Feb 2008 23:55:16 +0100, Arnd Bergmann wrote:
> On Tuesday 19 February 2008, Stefan Roese wrote:
> > On Tuesday 19 February 2008, Jean Delvare wrote:
> > >
> > > With this Kconfig change, "make menuconfig" lets me select the
> > > i2c-ibm_iic driver on x86_64, but it fails to build horribly. I think
> > > that you want to restrict the build to PPC machines somehow, or at
> > > least make sure that either IBM_OCP or OF support is present.
> >=20
> > How about this:
> >=20
> > -=A0=A0=A0=A0=A0=A0=A0depends on IBM_OCP
> > +=A0=A0=A0=A0=A0=A0=A0depends on 4xx
>=20
> I think we should allow it to be built on other platforms as well,
> as long as they have of_platform_device support.
>=20
> The Axon south bridge used on IBMs QS21 blade probably has an ibm_iic,
> even though it's managed by the firmware and we probably don't want
> to use it at this time, someone could use the same chip in a new
> design and actually do that.
>=20
> In general, I also like to make it possible to enable drivers just
> for the benefit of compile testing, even for stuff that you can't
> find in any existing HW configuration, so as long as it builds on
> a platform, I think we shouldn't forbid it:
Fine with me as long as the default is set appropriately (i.e. default
to not building the driver on archs/platforms where it builds but is
known to be useless.)
>=20
> - depends on IBM_OCP
> + depends on IBM_OCP || PPC_MERGE
--=20
Jean Delvare
next prev parent reply other threads:[~2008-02-20 6:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 17:05 [PATCH] i2c-ibm_iic driver Sean MacLennan
[not found] ` <47A14E23.50807@pikatech.com>
[not found] ` <20080214094516.1b958ae4@hyperion.delvare>
2008-02-16 4:07 ` [PATCH 1/2] " Sean MacLennan
2008-02-16 8:20 ` Jean Delvare
2008-02-16 4:11 ` [PATCH 2/2] " Sean MacLennan
2008-02-16 9:31 ` Jean Delvare
2008-02-16 20:54 ` Sean MacLennan
2008-02-17 10:52 ` Jean Delvare
2008-02-19 1:42 ` Sean MacLennan
2008-02-19 8:23 ` Jean Delvare
2008-02-19 8:59 ` Stefan Roese
2008-02-19 22:23 ` Sean MacLennan
2008-02-19 22:55 ` Arnd Bergmann
2008-02-19 23:18 ` Sean MacLennan
2008-02-19 23:41 ` Stephen Rothwell
2008-02-19 23:54 ` Arnd Bergmann
2008-02-20 6:57 ` Jean Delvare [this message]
2008-02-19 21:58 ` Sean MacLennan
2008-02-20 7:20 ` Jean Delvare
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=20080220075731.7675bbbb@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=arnd@arndb.de \
--cc=i2c@lm-sensors.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
--cc=sr@denx.de \
/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).