From: Wolfgang Denk <wd@denx.de>
To: "Kevin A. Sapp" <Kevin.Sapp@catapult.com>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Basic Config file
Date: Thu, 24 Apr 2003 22:18:31 +0200 [thread overview]
Message-ID: <20030424201836.56798C5E29@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 24 Apr 2003 16:00:06 EDT." <3EA84246.9050101@catapult.com>
In message <3EA84246.9050101@catapult.com> you wrote:
>
> Read the ELDK manual, however, did not see anything
> on the kernel configuration and building it. Went to
> kernelnewbies for that...anywhere else I can go for
> kernel configuration.
There is also http://www.denx.de/re/DPLG.html (but this does not
answer the details of kernel configuration - it only describes how to
use existing default configs). In all other cases you just have to
know what you are doing.
> Unresolveds are:
> va_to_pte and get_IMMR in traps.c
> the get_IMMR seems to be 8xx specific.
> va_to_pte is in several headers for asm code,
> but grep of the source tree does not show any
> implementations in *.[Sch]
It's a bug. Both EXPORT_SYMBOL()s are 8xx specific. Fixed in our
current CVS.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
A dog always bit deepest on the veterinary hand.
- Terry Pratchett, _Wyrd Sisters_
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-04-24 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00032EDD.C22236@borg.org>
2003-04-24 17:44 ` boot/simple in ROM? Jerry Van Baren
2003-04-24 18:02 ` Mark A. Greer
2003-04-24 18:11 ` Basic Config file Kevin A. Sapp
[not found] ` <3EA82B56.3070808@ecubics.com>
2003-04-24 20:00 ` Kevin A. Sapp
2003-04-24 20:18 ` Wolfgang Denk [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=20030424201836.56798C5E29@atlas.denx.de \
--to=wd@denx.de \
--cc=Kevin.Sapp@catapult.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).