From: Dan Malek <dan@embeddededge.com>
To: Jack Liu <Jack_liu@usish.com>
Cc: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: OpenPIC problem:OpenPIC not work at 0xFC000000 on MPC8245 platform
Date: Tue, 23 Mar 2004 10:23:19 -0500 [thread overview]
Message-ID: <40605667.5010600@embeddededge.com> (raw)
In-Reply-To: 200403230445.i2N4j7kZ030569@ms.usish.com
Jack Liu wrote:
> Can anybody give me your vaulable advice?
Why do you want to change it? The kernel assumes a MAP B configuration,
there are other memory mapping assumptions made for this to work as well.
Changing a single #define associated with memory mapping usually guarantees
nothing will work, as other configuration values are chosen to be
complimentary.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-03-23 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 4:44 OpenPIC problem:OpenPIC not work at 0xFC000000 on MPC8245 platform Jack Liu
2004-03-23 15:23 ` Dan Malek [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=40605667.5010600@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Jack_liu@usish.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).