From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2.6.12-rc2] ppc32: Fix building 32bit kernel for 64bit machines (Was: Re: linux 2.6.12-rc1-bk5 compilation error)
Date: Sat, 09 Apr 2005 09:47:20 +1000 [thread overview]
Message-ID: <1113004040.9568.385.camel@gaston> (raw)
In-Reply-To: <20050408153407.GZ3396@smtp.west.cox.net>
Go for it i
> When building a ppc32 MULTIPLATFORM kernel for a 64bit pmac, we try and
> build certain files or use certain functions that make no sense in that
> context. This catches the last of these.
>
> Signed-off-by: Tom Rini <trini@kernel.crashing.org>
>
> --- linux-2.6.orig/arch/ppc/platforms/pmac_cache.S
> +++ linux-2.6/arch/ppc/platforms/pmac_cache.S
> @@ -28,6 +28,9 @@
> */
>
> _GLOBAL(flush_disable_caches)
> +#ifndef CONFIG_6xx
> + blr
> +#else
> BEGIN_FTR_SECTION
> b flush_disable_745x
> END_FTR_SECTION_IFSET(CPU_FTR_SPEC7450)
> @@ -323,3 +326,4 @@ END_FTR_SECTION_IFSET(CPU_FTR_L3CR)
> mtmsr r11 /* restore DR and EE */
> isync
> blr
> +#endif /* CONFIG_6xx */
> --- linux-2.6.orig/arch/ppc/boot/simple/Makefile
> +++ linux-2.6/arch/ppc/boot/simple/Makefile
> @@ -123,10 +123,13 @@ zimageinitrd-$(pcore) := zImage.initrd
> end-$(pcore) := pcore
> cacheflag-$(pcore) := -include $(clear_L2_L3)
>
> +# Really only valid if CONFIG_6xx=y
> zimage-$(CONFIG_PPC_PREP) := zImage-PPLUS
> zimageinitrd-$(CONFIG_PPC_PREP) := zImage.initrd-PPLUS
> +ifeq ($(CONFIG_6xx),y)
> extra.o-$(CONFIG_PPC_PREP) := prepmap.o
> misc-$(CONFIG_PPC_PREP) += misc-prep.o mpc10x_memory.o
> +endif
> end-$(CONFIG_PPC_PREP) := prep
>
> end-$(CONFIG_SANDPOINT) := sandpoint
>
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
prev parent reply other threads:[~2005-04-08 23:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 10:32 linux 2.6.12-rc1-bk5 compilation error Jerome Glisse
2005-04-04 10:51 ` Jerome Glisse
2005-04-04 11:52 ` Jerome Glisse
2005-04-04 12:41 ` Benjamin Herrenschmidt
2005-04-04 19:11 ` Jerome Glisse
2005-04-04 23:12 ` Benjamin Herrenschmidt
2005-04-05 11:52 ` Jerome Glisse
2005-04-05 12:39 ` Andreas Schwab
2005-04-05 15:17 ` Jerome Glisse
2005-04-05 23:12 ` Benjamin Herrenschmidt
2005-04-05 23:25 ` Andreas Schwab
2005-04-05 23:11 ` Benjamin Herrenschmidt
2005-04-07 17:10 ` Tom Rini
2005-04-08 10:13 ` Jerome Glisse
2005-04-08 15:34 ` [PATCH 2.6.12-rc2] ppc32: Fix building 32bit kernel for 64bit machines (Was: Re: linux 2.6.12-rc1-bk5 compilation error) Tom Rini
2005-04-08 22:27 ` Jerome Glisse
2005-04-08 23:47 ` Benjamin Herrenschmidt [this message]
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=1113004040.9568.385.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).