From: Chris Zimman <chris@cryptoapps.com>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Status of 440GP support?
Date: Fri, 24 Jan 2003 10:38:02 -0800 [thread overview]
Message-ID: <20030124183802.GA21151@mail.cryptoapps.com> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B23621@penguin.adic.com>
On Fri, Jan 24, 2003 at 10:13:16AM -0800, brian.auld@adic.com wrote:
> 1) After looking at the source tree for linuxppc_2_4 and linuxppc_2_4_devel,
> it appears that 440GP support is only in linuxppc_2_4_devel. Does
> linuxppc2_4_devel mean "unstable", or is it simply the latest and greatest
> ppc kernel code for the 2.4 series that is stable.
The latter -- the trees just haven't been merged yet.
> 2) I'm going through iterations of make menuconfig (on linuxppc_2_4_devel
> tree) to try and get a kernel for the 440GP successfully built and am not
> having much success. Does anyone have a ".config" file that works that I
> could take a look at? Should it compile out of the box? I set up my
> cross-compile tools using the following:
> -> binutils-2.12.90.0.12
> -> gcc-3.2.1 (with gcc-3.2-crossppc.diff patch applied)
See arch/ppc/configs/ebony_defconfig
One way (there may be better ways) is:
cp arch/ppc/configs/ebony_defconfig .config
make oldconfig
> 3) I plan to use 'Das U-Boot' as my boot loader. Any other snafus/gotchas
> anyone would be willing to let me in on ahead of time??
Works fine for me.
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-24 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 18:13 Status of 440GP support? brian.auld
2003-01-24 18:38 ` Chris Zimman [this message]
2003-01-24 19:34 ` Eugene Surovegin
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=20030124183802.GA21151@mail.cryptoapps.com \
--to=chris@cryptoapps.com \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.