From: Hollis Blanchard <hollis@austin.ibm.com>
To: Vishwanath <vishwanath@mistralsoftware.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: IBM 440GP 36-bit addressing
Date: 26 Aug 2002 10:48:27 -0500 [thread overview]
Message-ID: <1030376908.1348.73.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <001101c24b3c$ae0cca70$faffa8c0@VISHWANATH>
On Sat, 2002-08-24 at 02:05, Vishwanath wrote:
>
> By going through the code, I understood that ioremap64() is used for mapping
> the 36-bit real address onto 32-bit effective address space. How this
> mapping information is conveyed to user applications ?
I don't understand the question. Do you mean "how does userspace know
what the kernel has ioremapped"? I don't think it does.
Do you mean "how can userspace map in a 36-bit real address"? The usual
(32-bit) way is to mmap(/dev/mem). I don't know if that will work with
36-bit addresses.
> If I am writing assembly instructions to access 440GP registers, do I have
> to pass 36-bit real address or 32-bit effective address ?
Do you mean a memory-mapped register, i.e. an on-chip peripheral like
the UART? If so, that's what we've been talking about. You must map the
36-bit real address into your 32-bit effective address space, then
access the effective address.
> Physical address map of 440GP provides information only about Real
> addresses. How can I convert these real addresses onto effective addresses
> ? Do I have to write a TLB entry regarding my addresses ?
Exactly, that's what I mean by "mapping".
Of course, some TLB entries may already have been set up for you by the
kernel or firmware. Whatever the case, you need to make sure there is a
TLB entry in place.
-Hollis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-26 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 15:00 IBM 440GP 36-bit addressing Vishwanath
2002-08-23 15:00 ` Hollis Blanchard
2002-08-24 7:05 ` Vishwanath
2002-08-26 15:48 ` Hollis Blanchard [this message]
2002-08-26 17:13 ` Eugene Surovegin
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=1030376908.1348.73.camel@granite.austin.ibm.com \
--to=hollis@austin.ibm.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=vishwanath@mistralsoftware.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