From: "Kevin A. Sapp" <Kevin.Sapp@catapult.com>
To: emanuel stiebler <emu@ecubics.com>,
linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Basic Config file
Date: Thu, 24 Apr 2003 16:00:06 -0400 [thread overview]
Message-ID: <3EA84246.9050101@catapult.com> (raw)
In-Reply-To: 3EA82B56.3070808@ecubics.com
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.
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]
Thanks
Kevin
emanuel stiebler wrote:
> Kevin A. Sapp wrote:
>
>>
>> Hello all,
>>
>> I recently downloaded and installed the ELDK under RedHat
>> 8 targeting a 74xx. Everything went pretty smooth (Thanks
>> Wolfgang!). I am utterly inexperienced at building the
>> kernel. This is the first one. I have everything compiling,
>> but getting various linker unresolves.
>
>
> Can you tell us more what unresolves you get ?
>
>> Can someone point me to or send a simple config file as an
>> example? As few components as possible would be great.
>
>
> Try the defaults first.
> I assume you read the documentation, right ?
> ;-)
>
> cheers
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-24 20:00 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 [this message]
2003-04-24 20:18 ` Wolfgang Denk
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=3EA84246.9050101@catapult.com \
--to=kevin.sapp@catapult.com \
--cc=emu@ecubics.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).