From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by ozlabs.org (Postfix) with ESMTP id F2BC9DDDFA for ; Thu, 12 Jul 2007 06:58:37 +1000 (EST) From: Arnd Bergmann To: linuxppc-dev@ozlabs.org Subject: Re: [RFC][PATCH 3/8] 4xx MMU Date: Wed, 11 Jul 2007 22:56:38 +0200 References: <1184161957.32199.52.camel@weaponx.rchland.ibm.com> <1184162179.32199.58.camel@weaponx.rchland.ibm.com> In-Reply-To: <1184162179.32199.58.camel@weaponx.rchland.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <200707112256.38312.arnd@arndb.de> List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wednesday 11 July 2007, Josh Boyer wrote: > +#elif defined(CONFIG_40x) > +/* 40x-style software loaded TLB */ > +# =A0include > =A0#elif defined(CONFIG_44x) > =A0/* 44x-style software loaded TLB */ > =A0# =A0include 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 > -#elif defined(CONFIG_44x) > -/* 44x-style software loaded TLB */ > -# include or=20 > +#elif defined(CONFIG_40x) > +/* 40x-style software loaded TLB */ > +# include > #elif defined(CONFIG_44x) > /* 44x-style software loaded TLB */ > # include 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 <><