Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261752AbTILQ4k (ORCPT ); Fri, 12 Sep 2003 12:56:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261755AbTILQ4k (ORCPT ); Fri, 12 Sep 2003 12:56:40 -0400 Received: from fed1mtao04.cox.net ([68.6.19.241]:35565 "EHLO fed1mtao04.cox.net") by vger.kernel.org with ESMTP id S261752AbTILQ4g (ORCPT ); Fri, 12 Sep 2003 12:56:36 -0400 Date: Fri, 12 Sep 2003 09:56:35 -0700 From: Tom Rini To: Judith Lebzelter Cc: linux-kernel@vger.kernel.org, plm-devel@lists.sourceforge.net Subject: Re: PowerPC Cross-compile of 2.6 kernels Message-ID: <20030912165635.GJ13672@ip68-0-152-218.tc.ph.cox.net> References: <20030912150611.GE13672@ip68-0-152-218.tc.ph.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2749 Lines: 82 On Fri, Sep 12, 2003 at 09:52:23AM -0700, Judith Lebzelter wrote: > On Fri, 12 Sep 2003, Tom Rini wrote: > > > On Wed, Sep 10, 2003 at 04:41:05PM -0700, Judith Lebzelter wrote: > > > Hello, > > > > > > In response to requests at OLS, we've added cross-compile > > > capability to the PLM, and the first architecture > > > implemented is PowerPC. The powerpc code is > > > generated via a cross-compiler set up using Dan > > > Kegels's crosstool-0.22 on an i386 host using gcc-3.3.1, > > > glibc-2.3.2 and built for the powerpc-750. > > > > > > The filter run is the compile regress developed by John > > > Cherry at OSDL. Refer to his prior mail on lkml for the > > > results of this filter on ia386 and IA64. > > > > > > Look at > > > http://www.osdl.org/plm-cgi/plm?module=search > > > and look up linux-2.6.0-test5 or any later kernels for the > > > results of this filter under 'PPC-Cross Compile Regress'. > > > > > > Does anyone have any input regarding requests for > > > additional architectures or improvements to the > > > filters? Please cc me in any responses to lkml as I do > > > not currently monitor this list, though other OSDL > > > employees do. > > > > Is there any way to seed the config so that it will override what > > allmodconfig (or allyesconfig) sets? Both of these targets by nature > > pick an 'odd' machine to compile for. > > > > The 'allmodconfig' is what we run, and it chose > # > # Platform support > # > CONFIG_PPC=y > CONFIG_PPC32=y > CONFIG_6xx=y > > # > # IBM 4xx options > # > CONFIG_EMBEDDEDBOOT=y > CONFIG_8260=y > CONFIG_PPC_STD_MMU=y > CONFIG_SERIAL_CONSOLE=y > # CONFIG_EST8260 is not set > # CONFIG_SBS8260 is not set > # CONFIG_RPX6 is not set > # CONFIG_TQM8260 is not set > CONFIG_WILLOW_1=y > > I had to change this to do TQM8260 because the header file willow.h is > missing and the number of errors for this one file made the compile look > far worse than it actually was. If you suggest something, I will > change it. Don't select 8260 at all, and then the default choice should be CONFIG_PPC_MULTIPLATFORM, which is normally the best choice. I suppose this is more incentive for removing the rather bogus distinction made for 8260 boards. > I also realize that my output should include any changes I make to the > configurations and have that changed right away. > > We are also adding the 'allyesconfig' and will apply the same platform > changes as to 'allmodconfig'. Okay, thanks. -- Tom Rini http://gate.crashing.org/~trini/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/