From: "Frank Smith" <smith@amirix.com>
To: <clark@esteem.com>, <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: PPCBoot memory mapping problems
Date: Fri, 18 Aug 2000 23:10:44 -0300 [thread overview]
Message-ID: <00Aug18.231049adt.7303@dragon.appliedmicro.ns.ca> (raw)
In-Reply-To: <1.5.4.32.20000819004501.006984e4@pop.esteem.com>
> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of
> clark@esteem.com
> Sent: Friday, August 18, 2000 9:49 PM
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: PPCBoot memory mapping problems
>
...
>
> Our board boots up checks the kernels CRC then uncompresses it. It
> then jumps to 0x0000000C. A little bit later it then jumps to some address
> 0xC000???? and faults.
>
> Is this what it is supposed to do? Am I supossed to have the RAM
Jump to 0xC000???? Yup. Fault? No.
> mapped at 0xC0000000? If it loads at address 0 how do I remap it to
> 0xC0000000 once the kernel starts? Is there any way to force the kernel to
Basically, the kernel boot process should be doing this *for* you.
Part of the kernel boot process is to set up a memory mapping from
virtual C0000000 to physical 00000000, and then enable address translation.
This is done in arch/ppc/kernel/head.S using the BAT registers.
> run in lower memory?
I doubt it. It shouldn't be necessary, tho.
>
>
> Thanks in advance for any help.
>
> Conn Clark
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-19 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-19 0:45 PPCBoot memory mapping problems clark
2000-08-19 2:10 ` Frank Smith [this message]
2000-08-19 8:26 ` Wolfgang Denk
2000-08-19 8:26 ` Wolfgang Denk
2000-08-21 11:24 ` Jerry Van Baren
2000-08-21 11:52 ` diekema_jon
2000-08-21 13:25 ` 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=00Aug18.231049adt.7303@dragon.appliedmicro.ns.ca \
--to=smith@amirix.com \
--cc=clark@esteem.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).