From: Nicolas Mederle <mederle_nicolas@yahoo.fr>
To: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: PageFault when I write in the Serial registers, MMU ?
Date: Wed, 11 Jul 2007 17:39:41 +0200 [thread overview]
Message-ID: <4694F9BD.4090406@yahoo.fr> (raw)
Hi,
I am porting linux on a custom board equipped with a PPC750, and I
will like to have some advices on the MMU. I used the powerpc arch, and
I built my device tree.
I will like to know in which files we can configure the
authorizations access for the I/O registers. When I use the function
md_ppc.progress, I have a data access fault. I modified the head. S
files, for add the BAT config. But I think that it is not correct, and
that it is possible to do it elsewhere (platform_init?). Moreover the
kernel modify the MMU config, it removes the BATs, and configures the
Registers Segments. So, must I remake the configuration? Or is it
possible to indicate, at the beginning, which space is reserved for I/O?
I studied several patch (sandpoint, PrPMC2800) but none configures
really the MMU for I/O registers. In the same way, I read several books,
but I am not able to have information that I seek, therefore I am really
blocked. I warmly thank you for the assistance which you will be able to
bring to me.
Mapping : 0x0000 0000 -> 0x0FFF FFFF : RAM
0x2000 0000 -> 0x201F FFFF : ASIC (
UART, DMA, GPIO, PIC...)
0x8000 0000 -> 0x8FFF FFFF : PCI
0xF000 0000 -> 0xFFFF FFFF : Flash
The kernel is load at 0x0, an the system is a Run In Memory.
Currently, I don't use the flash.
Best regards,
Nicolas MEDERLE
--
Cordialement,
Nicolas MEDERLE.
next reply other threads:[~2007-07-11 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:39 Nicolas Mederle [this message]
2007-07-11 15:53 ` PageFault when I write in the Serial registers, MMU ? Laurent Pinchart
2007-07-11 16:32 ` Bhupender Saharan
2007-07-11 17:51 ` Josh Boyer
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=4694F9BD.4090406@yahoo.fr \
--to=mederle_nicolas@yahoo.fr \
--cc=linuxppc-dev@ozlabs.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.