From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org
Subject: Re: [RFC][PATCH 3/8] 4xx MMU
Date: Wed, 11 Jul 2007 22:56:38 +0200 [thread overview]
Message-ID: <200707112256.38312.arnd@arndb.de> (raw)
In-Reply-To: <1184162179.32199.58.camel@weaponx.rchland.ibm.com>
On Wednesday 11 July 2007, Josh Boyer wrote:
> +#elif defined(CONFIG_40x)
> +/* 40x-style software loaded TLB */
> +# =A0include <asm/mmu-4xx.h>
> =A0#elif defined(CONFIG_44x)
> =A0/* 44x-style software loaded TLB */
> =A0# =A0include <asm/mmu-44x.h>
If you call it mmu-4xx, shouldn't it be used
for 44x as well? I would think this either
should be
> +#elif defined(CONFIG_4xx)
> +/* 40x-style software loaded TLB */
> +# include <asm/mmu-4xx.h>
> -#elif defined(CONFIG_44x)
> -/* 44x-style software loaded TLB */
> -# include <asm/mmu-44x.h>
or=20
> +#elif defined(CONFIG_40x)
> +/* 40x-style software loaded TLB */
> +# include <asm/mmu-40x.h>
> #elif defined(CONFIG_44x)
> /* 44x-style software loaded TLB */
> # include <asm/mmu-44x.h>
Is it actually feasible to get to a point where
you can build a kernel that boots on both
40x and 44x, or is it just too different?
Arnd <><
next prev parent reply other threads:[~2007-07-11 20:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 13:52 [RFC][PATCH 0/8] arch/powerpc support for Walnut Board Josh Boyer
2007-07-11 13:53 ` [RFC][PATCH 1/8] 4xx Kconfig cleanup Josh Boyer
2007-07-11 13:55 ` [RFC][PATCH 2/8] 4xx boot wrapper reworks Josh Boyer
2007-07-11 13:56 ` [RFC][PATCH 3/8] 4xx MMU Josh Boyer
2007-07-11 20:56 ` Arnd Bergmann [this message]
2007-07-11 21:15 ` Josh Boyer
2007-07-12 7:09 ` Kumar Gala
2007-07-12 12:40 ` Josh Boyer
2007-07-11 13:57 ` [RFC][PATCH 4/8] 4xx decrementer fixes Josh Boyer
2007-07-11 13:58 ` [RFC][PATCH 5/8] Fix 4xx build Josh Boyer
2007-07-11 21:00 ` Arnd Bergmann
2007-07-11 13:59 ` [RFC][PATCH 6/8] Walnut DTS Josh Boyer
2007-07-11 14:26 ` Stefan Roese
2007-07-11 14:37 ` Josh Boyer
2007-07-11 17:49 ` Segher Boessenkool
2007-07-11 17:55 ` Josh Boyer
2007-07-11 18:07 ` Segher Boessenkool
2007-07-18 1:02 ` David Gibson
2007-07-12 15:13 ` Yoder Stuart-B08248
2007-07-16 14:34 ` Segher Boessenkool
2007-07-16 21:47 ` Benjamin Herrenschmidt
2007-07-16 21:55 ` Scott Wood
2007-07-16 22:11 ` Benjamin Herrenschmidt
2007-07-16 22:18 ` Scott Wood
2007-07-16 22:34 ` Benjamin Herrenschmidt
2007-07-16 21:55 ` Yoder Stuart-B08248
2007-07-16 22:12 ` Benjamin Herrenschmidt
2007-07-17 2:39 ` Josh Boyer
2007-07-17 14:26 ` Segher Boessenkool
2007-07-17 14:15 ` Segher Boessenkool
2007-07-17 21:25 ` Benjamin Herrenschmidt
2007-07-17 22:25 ` Scott Wood
2007-07-17 22:58 ` Benjamin Herrenschmidt
2007-07-18 13:53 ` Segher Boessenkool
2007-07-18 16:47 ` Scott Wood
2007-07-19 16:54 ` Segher Boessenkool
2007-07-18 13:48 ` Segher Boessenkool
2007-07-11 14:02 ` [RFC][PATCH 7/8] Walnut defconfig Josh Boyer
2007-07-11 14:03 ` [RFC][PATCH 8/8] Walnut board support Josh Boyer
2007-07-11 14:04 ` [RFC][PATCH 9/8] Walnut zImage wrapper Josh Boyer
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=200707112256.38312.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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