From: Wolfgang Denk <wd@denx.de>
To: Yu Bo-BOYU1 <Bo.Yu@motorola.com>
Cc: acurtis@onz.com, Flavio Pereira <fpereira@azisa.com>,
linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 8260 configuration
Date: Wed, 02 Oct 2002 17:07:06 +0200 [thread overview]
Message-ID: <20021002150711.6DC63FA99@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 02 Oct 2002 09:54:34 CDT." <0B0A39652BB0D411BCCF00508B9512EC08AEB3FE@tx14exm05.ftw.mot.com>
In message <0B0A39652BB0D411BCCF00508B9512EC08AEB3FE@tx14exm05.ftw.mot.com> you wrote:
> Is 0x0 the real physical address or logical address ? As far as
It's the real physical address.
> Since vxWorks (5.4) has no virtual memory support and the exception
> base address is mapped to 0x0 already, starting linux kernel at 0x0
> would mean there is no exception handling capability at least at
> the very beginning.
Why not? When you copy the Linux kernel image to low memory you
include the Linux trap handlers, of course.
Not that they would do you any good in the very early boot stage,
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
It's hard to make a program foolproof because fools are so ingenious.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-10-02 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0B0A39652BB0D411BCCF00508B9512EC08AEB3FE@tx14exm05.ftw.mot.com>
2002-10-02 15:07 ` Wolfgang Denk [this message]
2002-10-07 14:39 8260 configuration Yu Bo-BOYU1
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 14:43 Yu Bo-BOYU1
2002-10-02 18:10 Yu Bo-BOYU1
2002-10-02 21:40 ` Joe Hamman
2002-10-02 7:22 Flavio Pereira
2002-10-02 14:04 ` Allen Curtis
2002-10-02 14:27 ` Allen Curtis
2002-10-02 14:47 ` Wolfgang Denk
2002-10-02 15:07 ` Allen Curtis
2002-10-02 1:07 Yu Bo-BOYU1
2002-10-02 7:09 ` 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=20021002150711.6DC63FA99@denx.denx.de \
--to=wd@denx.de \
--cc=Bo.Yu@motorola.com \
--cc=acurtis@onz.com \
--cc=fpereira@azisa.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).