All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Porter <porter@cox.net>
To: Vishwanath <vishwanath@mistralsoftware.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: ioremap64 and remap_page_range in 440GP
Date: Sun, 5 Jan 2003 21:10:07 -0700	[thread overview]
Message-ID: <20030105211007.C22675@home.com> (raw)
In-Reply-To: <001801c2b161$5fa973c0$faffa8c0@VISHWANATH>; from vishwanath@mistralsoftware.com on Wed, Jan 01, 2003 at 12:15:29PM +0530


On Wed, Jan 01, 2003 at 12:15:29PM +0530, Vishwanath wrote:
>
> Hi All,
>
> In PPC Linux, to bring a particular IO page onto Linux addressing space, we
> use ioremap64(). Is my understanding correct? If I want to map this remapped

Yes.

> address on user space, I have to use  remap_page_range() of kernel in my
> driver.  remap_page_range() takes a 32-bit physical address as argument. But
> in 440GP, all addresses are 36-bit with respect to processor. Is there any
> 64-bit equivalent of remap_page_range(). If it exists, how to use it?

There's a patch to make remap_page_range() use a phys_addr_t and to use
the same bigphys fixups that ioremap() on 440gp uses.  Part of it is
a bit of hack which is why it's not being commited.  See the changeset
description in linuxppc_2_4_devel or linuxppc-2.5 for a pointer to
pick up the patch.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

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

      reply	other threads:[~2003-01-06  4:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01  6:45 ioremap64 and remap_page_range in 440GP Vishwanath
2003-01-06  4:10 ` Matt Porter [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=20030105211007.C22675@home.com \
    --to=porter@cox.net \
    --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 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.