From: Matt Porter <mporter@mvista.com>
To: Stephen Noftall <stephenn@lcsaudio.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Using 2_4_devel to build a kernel for the 8240
Date: Thu, 25 Apr 2002 14:54:18 -0700 [thread overview]
Message-ID: <20020425145418.A7189@home.com> (raw)
In-Reply-To: <002401c1eca1$c8260830$61012ac7@snbeast>; from stephenn@lcsaudio.com on Thu, Apr 25, 2002 at 02:40:11PM -0700
On Thu, Apr 25, 2002 at 02:40:11PM -0700, Stephen Noftall wrote:
>
> Hello;
>
> I am using the latest bitkeeper PPC 2_4_devel kernel, and want to configure it
> for the 8240.
>
> When I run menuconfig, I can see "Sandpoint X3" and "8260" selections, but no
> 8240 specific selections.
>
> What options should I select to enable 8240 support? I am guessing "Sandpoint
> X3", is this right? The board is a custom 8240, with Ethernet and SCSI PCI
> chipsets, but no serial or ISA components. We have previously gotten a 2.3.16
> kernel to work on it.
The Processor Type option text for CONFIG_6xx is wrong. It should say
82xx instead of 8260. Select 6xx/7xx/74xx/8260 for now since you
have a "classic PPC" core.
Sandpoint is a board. It does not "enable" 8240 support. An 8240 is
more or less a 603e + MPC10x bridge for software purposes. Add
an entry for your custom board and use mpc10x_common.c like other
examples in 2_4_devel.
Regards,
--
Matt Porter
MontaVista Software, Inc.
mporter@mvista.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-04-25 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200204252126.QAA11192@lists.linuxppc.org>
2002-04-25 21:40 ` Using 2_4_devel to build a kernel for the 8240 Stephen Noftall
2002-04-25 21:43 ` Mark A. Greer
2002-04-25 21:54 ` Matt Porter [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=20020425145418.A7189@home.com \
--to=mporter@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stephenn@lcsaudio.com \
/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).