linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Judith Lebzelter <judith@osdl.org>
Cc: Cort Dougan <cort@ftsoj.fsmlabs.com>,
	linux-kernel@vger.kernel.org, plm-devel@lists.sourceforge.net
Subject: Re: PowerPC Cross-compile of 2.6 kernels
Date: Mon, 15 Sep 2003 14:22:34 -0700	[thread overview]
Message-ID: <20030915212234.GB9102@ip68-0-152-218.tc.ph.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0309151318010.631-100000@osdlab.pdx.osdl.net>

On Mon, Sep 15, 2003 at 02:12:26PM -0700, Judith Lebzelter wrote:
> On Fri, 12 Sep 2003, Cort Dougan wrote:
> 
> > It would be nice to see the 4xx and 8xx chips being tested.  There are a
> > lot of rarely tested configurations and targets in the PPC kernel.
> 
> I could run a simpler compile filter, one compile that counts and
> prints all the errors and warnings, on these extra platforms.  Did you
> have any specific platform in mind?  40x give me 'walnut' and 8xx gives
> me 'rpx-lite' if I do 'make defconfig' followed by 'make oldconfig' where
> I set the main platform (to 40x or 8xx) and accept all the default
> options.

'Walnut' is a good 40x platform.  I wouldn't worry about 8xx right now,
however.

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2003-09-15 21:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 23:41 PowerPC Cross-compile of 2.6 kernels Judith Lebzelter
2003-09-12 15:06 ` Tom Rini
2003-09-12 16:52   ` Judith Lebzelter
2003-09-12 16:56     ` Tom Rini
2003-09-12 20:13       ` Judith Lebzelter
2003-09-12 21:32         ` Tom Rini
2003-09-13  0:55           ` Cort Dougan
2003-09-15 21:12             ` Judith Lebzelter
2003-09-15 21:22               ` Tom Rini [this message]
2003-09-29 16:54           ` Tom Rini
2003-09-29 20:21             ` Judith Lebzelter
2003-09-29 20:34               ` Tom Rini

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=20030915212234.GB9102@ip68-0-152-218.tc.ph.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=cort@ftsoj.fsmlabs.com \
    --cc=judith@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plm-devel@lists.sourceforge.net \
    /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).