From: Matt Porter <porter@cox.net>
To: Claudia Salzberg <sentinel@jump.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: mapping back to 36 bit physical
Date: Sun, 5 Jan 2003 20:22:02 -0700 [thread overview]
Message-ID: <20030105202202.A22675@home.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0212181358270.23138-100000@grandmaster.protagonist.org>; from sentinel@jump.net on Wed, Dec 18, 2002 at 02:07:45PM +0600
On Wed, Dec 18, 2002 at 02:07:45PM +0600, Claudia Salzberg wrote:
>
> Greetings.
> How does one go about aquiring the 36-bit physical address on a 440XX if
> you have the corresponding va from an ioremap (when your driver is not
> the one that did the ioremap so that you don't have the pa saved)? I see
> that ioremap does support 36-bit I/O mapping but _va and _pa only play
> with unsigned long's. So does iopa. So do the virt_to_* 's I was able
> to find. Also, does anyone have plans for incorporating memory access
> hooks above 4GB address space?
Everything is in the linuxppc-2.5 and linuxppc_2_4_devel to support all
normal kernel functionality with the exception of remap_page_range().
As part of a recent checkin, the commit notice gave a reference to an
ftp site to get a remap_page_range() 64-bit patch. Check your changesets
or linuxppc-commit list archives.
You need to save the pa. virt_to_* and friends are only valid for
kernel lowmem addresses as per Documentation/IO-mapping.txt. Regardless,
all new drivers should be using the dma mapping api and saving the pa
as required.
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/
prev parent reply other threads:[~2003-01-06 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 8:07 mapping back to 36 bit physical Claudia Salzberg
2002-12-19 18:30 ` Tom Rini
2003-01-06 3:22 ` 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=20030105202202.A22675@home.com \
--to=porter@cox.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sentinel@jump.net \
/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.