From: "Michael J. Accetta" <mja@laurelnetworks.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: mpc755, sandpoint port and 1Gb of ram
Date: Thu, 03 Jul 2003 12:31:52 -0400 (EDT) [thread overview]
Message-ID: <14511.1057249912@mja-pc-linux.dhcp.pit.laurelnetworks.com> (raw)
In-Reply-To: Your message of "Wed, 02 Jul 2003 10:25:31 PDT." <3F03158B.7090706@mvista.com>
Mark
Its probably just a personal preference but I think changing the mapping
and leaving PKMAP_BASE alone is a better way. Someday I will do that
for the sandpoint port.
In short, what you did, assuming you did it properly, should work fine.
Thanks much for the confirmation. That did seem less risky than
changing the sandpoint I/O mapping without understanding where all the
I/O addresses were expected to be (which I don't). I would concur,
though, that that approach seems a better someday solution.
I am using the configure process to change PKMAP_BASE.
Mike
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-07-03 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 2:21 mpc755, sandpoint port and 1Gb of ram Michael J. Accetta
2003-07-02 17:25 ` Mark A. Greer
2003-07-03 16:31 ` Michael J. Accetta [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=14511.1057249912@mja-pc-linux.dhcp.pit.laurelnetworks.com \
--to=mja@laurelnetworks.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.com \
/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).