From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: asm-ppc header issues when building ARCH=powerpc
Date: Wed, 22 Aug 2007 14:30:47 -0500 [thread overview]
Message-ID: <20070822143047.6c8a0d4e@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <75EDD900-3B5E-4D08-9311-13B6510EDE6E@kernel.crashing.org>
On Wed, 22 Aug 2007 10:19:21 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:
> Guys,
>
> I was wondering if I could get your help with looking at the
> following lists and determining if we have an issue or not related
> the following files:
>
> Getting some classification on these would be good. Possibly
> classifications, doesn't build in ARCH=powerpc, remove include, real
> issue, etc.
Sure.
> ./drivers/i2c/busses/i2c-ibm_iic.c:#include <asm/ocp.h>
> ./drivers/i2c/busses/i2c-ibm_iic.c:#include <asm/ibm4xx.h>
These one depends on IBM_OCP in Kconfig. We don't select/enable that on
any existing arch/powerpc 4xx stuff so it won't be built anyway.
> ./drivers/mtd/maps/ebony.c:#include <asm/ibm44x.h>
This one depends on !PPC_MERGE in Kconfig. It can be ignored.
> ./drivers/net/ibm_emac/ibm_emac_core.c:#include <asm/ocp.h>
> ./drivers/net/ibm_emac/ibm_emac_core.h:#include <asm/ocp.h>
> ./drivers/net/ibm_emac/ibm_emac_tah.h:#include <asm/ocp.h>
> ./drivers/net/ibm_emac/ibm_emac_phy.c:#include <asm/ocp.h>
> ./drivers/net/ibm_emac/ibm_emac_mal.c:#include <asm/ocp.h>
> ./drivers/net/ibm_emac/ibm_emac_zmii.h:#include <asm/ocp.h>
These are guarded by !PPC_MERGE in Kconfig, so they won't be built in
arch/powerpc. And we all know we're waiting for the ibm_newemac driver
to show up for arch/powerpc... ;)
> ./drivers/mtd/maps/walnut.c:#include <asm/ibm4xx.h>
> ./drivers/mtd/maps/ocotea.c:#include <asm/ibm44x.h>
> ./drivers/mtd/nand/ndfc.c:#include <asm/ibm44x.h>
ndfc.c doesn't even need asm/ibm44x.h in arch/ppc. It could be removed
safely. However, the build will fail on arch/powerpc because of the
call to ioremap64. So we should guard it for now, until I get the
flash stuff working on Bamboo and come up with something better.
The patch below fixes these, similar to how drivers/mtd/maps/ebony.c is
guarded.
josh
[POWERPC] Don't build arch/ppc dependent drivers in arch/powerpc
These drivers are specific to 4xx support in arch/ppc at the moment. Make
sure they don't get built on arch/powerpc.
Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
---
drivers/mtd/maps/Kconfig | 4 ++--
drivers/mtd/nand/Kconfig | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--- linux-2.6.orig/drivers/mtd/maps/Kconfig
+++ linux-2.6/drivers/mtd/maps/Kconfig
@@ -354,7 +354,7 @@ config MTD_CFI_FLAGADM
config MTD_WALNUT
tristate "Flash device mapped on IBM 405GP Walnut"
- depends on MTD_JEDECPROBE && WALNUT
+ depends on MTD_JEDECPROBE && WALNUT && !PPC_MERGE
help
This enables access routines for the flash chips on the IBM 405GP
Walnut board. If you have one of these boards and would like to
@@ -370,7 +370,7 @@ config MTD_EBONY
config MTD_OCOTEA
tristate "Flash devices mapped on IBM 440GX Ocotea"
- depends on MTD_CFI && OCOTEA
+ depends on MTD_CFI && OCOTEA && !PPC_MERGE
help
This enables access routines for the flash chips on the IBM 440GX
Ocotea board. If you have one of these boards and would like to
--- linux-2.6.orig/drivers/mtd/nand/Kconfig
+++ linux-2.6/drivers/mtd/nand/Kconfig
@@ -134,7 +134,7 @@ config MTD_NAND_S3C2410_HWECC
config MTD_NAND_NDFC
tristate "NDFC NanD Flash Controller"
- depends on 44x
+ depends on 44x && !PPC_MERGE
select MTD_NAND_ECC_SMC
help
NDFC Nand Flash Controllers are integrated in EP44x SoCs
next prev parent reply other threads:[~2007-08-22 19:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 15:19 asm-ppc header issues when building ARCH=powerpc Kumar Gala
2007-08-22 16:01 ` Scott Wood
2007-08-22 19:30 ` Josh Boyer [this message]
2007-08-23 2:49 ` David Gibson
2007-08-23 3:09 ` Kumar Gala
2007-08-23 2:47 ` David Gibson
2007-08-23 3:22 ` Kumar Gala
2007-08-23 17:33 ` Scott Wood
2007-08-23 18:00 ` Kumar Gala
2007-08-23 3:33 ` Kumar Gala
2007-08-23 3:33 ` David Gibson
2007-08-23 4:16 ` Kumar Gala
2007-08-23 9:47 ` Geert Uytterhoeven
2007-08-23 18:56 ` Brad Boyer
2007-08-24 7:10 ` Geert Uytterhoeven
2007-08-24 7:24 ` Kumar Gala
2007-08-24 7:24 ` Geert Uytterhoeven
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=20070822143047.6c8a0d4e@weaponx.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).