From: "Allen Curtis" <acurtis@onz.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Stable BK for 405GP Walnut?
Date: Tue, 21 May 2002 21:35:23 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFAEGJDHAA.acurtis@onz.com> (raw)
I retrieved the latest linuxppc_2_4 source code with the intentions of
building a Walnut kernel. We are looking to build the next shippable kernel
ASAP so we thought it would be best to use the "stable" version.
Unfortunately when I tried to configure and compile we encountered several
surprises:
1. All the 405GP stuff is missing from the non-development tree. (PCI, DMA,
all the OCP support such as Ethernet)
2. Compile errors in ppc4xx_pic.c, invalid relocation type messages. (This
is something that I can solve with a little time.)
What should I use to build a Walnut kernel?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-05-22 4:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 4:35 Allen Curtis [this message]
2002-05-22 17:21 ` Stable BK for 405GP Walnut? Armin
2002-05-23 2:21 ` Allen Curtis
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=NCBBIINEHIPFGJPLBEIFAEGJDHAA.acurtis@onz.com \
--to=acurtis@onz.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 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).