LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@austin.ibm.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: IBM 440GP 36-bit addressing
Date: 23 Aug 2002 10:00:23 -0500	[thread overview]
Message-ID: <1030114823.8559.37.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <001501c24ab5$daee9500$faffa8c0@VISHWANATH>


On Fri, 2002-08-23 at 10:00, Vishwanath wrote:
>
> I am new to PPC Linux. I am working on IBM 440 GP board. I am using
> MontaVista Linux source code. I didn't understand how 36-bit addressing is
> taken care in this code. If an application has to access the a memory
> location in SDRAM of 440 GP or its internal peripheral registers, whether it
> has to pass 36-bit address or normal 32-bit address.

It's a 36-bit real address space, but 32-bit effective (aka "virtual").
Applications, which run entirely in effective address space, have no
reason to think about such things and require no modification.

The kernel has to care about the real address space, mostly when you
want to ioremap (all the on-chip peripheral addresses are higher than
4GB as I recall) a 36-bit real address to a 32-bit effective address so
you can use it in the kernel (which also runs in effective mode).

-Hollis


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-08-23 15:00 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 [this message]
2002-08-24  7:05   ` Vishwanath
2002-08-26 15:48     ` Hollis Blanchard
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=1030114823.8559.37.camel@granite.austin.ibm.com \
    --to=hollis@austin.ibm.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