From: Ralph Blach <rcblach@raleigh.ibm.com>
To: Daris A Nevil <dnevil@snmc.com>
Cc: Graham Stoney <greyham@research.canon.com.au>,
Daniel Wu <Daniel.Wu@alcatel.com.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Porting LinuxPPC
Date: Fri, 19 May 2000 09:09:31 -0400 [thread overview]
Message-ID: <39253D0B.F9AF86EE@raleigh.ibm.com> (raw)
In-Reply-To: 39253A48.24B90117@snmc.com
Daris,
I disagree. I beleive that the Kernel load simply must be above
0x80000000.
And I you want to put a lot of memory in one of these systems, it had
better be movable down from 0xc0000000. On the IBM405gp and I assume,
the 8xx systems, all of real memory is pinned
into a to TLB's. Well, if one can't move the memory base down the the
real memory available is from 0xc0000000 to whereve the IO starts. In
the IBM405gp, this is at 0xe80000000.
Chip
Daris A Nevil wrote:
>
> Graham,
>
> I fell vicitm to the same mistake when I was writing boot code
> for MPC850. I think adding that to the HOWTO is a great
> idea. It would have save me 2 or 3 weeks of effort :-).
>
> Daris Nevil
> SiSIC Inc/SNMC
>
> Graham Stoney wrote:
>
> > Hi Daniel,
> >
> > Daniel Wu writes:
> > > I compiled the mpc8xx-2.2.13 sources using the attached configuration for a
> > > MPC860T based board with 32MB of RAM. The output vmlinux file was downloaded
> > > to the target using a BDM debugger. I changed the KERNELLOAD and KERNELBASE
> > > to 1000000 instead of c0000000 so that the code is located at the start of
> > > the 16MB region.
> >
> > To quote Grant Erickson in
> > http://lists.linuxppc.org/listarcs/linuxppc-embedded/200001/msg00123.html:
> >
> > "You don't ever want to change KERNELLOAD or KERNELBASE, otherwise the
> > virtual memory and MMU code will all break."
> >
> > This seems to be a common error, so I might add mention of it in the HOWTO.
> >
> > Regards,
> > Graham
> >
>
> --
>
> Daris A Nevil
> SiSIC, Inc., f.k.a. Simple Network Magic Corporation
> 401 Kentucky Lane
> McKinney, TX 75069
> 214-793-7757
> dnevil@snmc.com
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-19 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 4:31 Porting LinuxPPC Daniel Wu
2000-05-19 5:10 ` Graham Stoney
2000-05-19 8:09 ` Daniel Wu
2000-05-19 8:19 ` Graham Stoney
2000-05-19 11:07 ` Dan A. Dickey
2000-05-19 12:57 ` Daris A Nevil
2000-05-19 13:09 ` Ralph Blach [this message]
2000-05-19 15:50 ` Dan Malek
2000-05-23 7:18 ` Daniel Wu
2000-05-23 21:01 ` Richard Hendricks
2000-05-23 22:00 ` Richard Hendricks
[not found] ` <392A3147.3A9AC5C2@alcatel.com.au>
2000-05-30 7:49 ` Daniel Wu
2000-05-30 18:54 ` Tom Roberts
2000-05-19 11:39 ` Ralph Blach
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=39253D0B.F9AF86EE@raleigh.ibm.com \
--to=rcblach@raleigh.ibm.com \
--cc=Daniel.Wu@alcatel.com.au \
--cc=dnevil@snmc.com \
--cc=greyham@research.canon.com.au \
--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).