From: Scott Wood <scottwood@freescale.com>
To: "Qin, Laigui (GE EntSol, Security)" <laigui.qin@ge.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: NAND access fail after MMU enabled when booting linux
Date: Mon, 23 Jun 2008 12:00:28 -0500 [thread overview]
Message-ID: <485FD6AC.6010605@freescale.com> (raw)
In-Reply-To: <A9D89E0D76AFF24B9441851F2AC72D7203E7E23C@BANMLVEM05.e2k.ad.ge.com>
Qin, Laigui (GE EntSol, Security) wrote:
> I am facing a MMU related problem when porting Linux to my custom board
> with Coldfire M5445x processor. The observation is that* the nand Bus
> chip select/WE/RE become 100 times longer than normal when MMU enabled*.
> I just can not understand this...
Coldfire is m68k; this list is for powerpc.
> Look into my driver codes, I use the virtual address (0xe0000000)
> applied from ioremap() kernel function.
>
> 136 /* map physical address */
> 137 this->IO_ADDR_R = this->IO_ADDR_W = ioremap(0x00000000, 1024);
> 138 if (!this->IO_ADDR_R) {
> 139 printk(KERN_WARNING "ioremap micron NAND @0x00000000
> failed\n");
Is it really at address zero, or is that where your RAM is?
-Scott
prev parent reply other threads:[~2008-06-23 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 3:06 NAND access fail after MMU enabled when booting linux Qin, Laigui (GE EntSol, Security)
2008-06-23 17:00 ` Scott Wood [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=485FD6AC.6010605@freescale.com \
--to=scottwood@freescale.com \
--cc=laigui.qin@ge.com \
--cc=linuxppc-embedded@ozlabs.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).