From: ashish anand <ashisha@india.infogain.com>
To: Goddeeris Frederic <Frederic.Goddeeris@siemens.atea.be>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: "Kernel logical address" vs "Physical"
Date: Fri, 14 Sep 2001 12:19:30 +0530 [thread overview]
Message-ID: <3BA1A87A.63F07742@india.infogain.com> (raw)
In-Reply-To: 6B546A602AD2D211BFF00008C7A42889041D6BE4@hrtades2.atea.be
Goddeeris Frederic wrote:
>
> So the key is that by address is above ioremap_base. That I initially got
> away with not using ioremap is a coincidence? Right?
>
> Where could I find a complete discussion of how all this is organized? The
> documents I find are or very vague, or explain a small issue and suppose you
> have already solid knowledge about it.
ioremap_base is not unique for every board.
but 0xfaxxxxxx is above ioremap_base for most of situations.
you have to go for high level browsing of memory initialisation codes
in your source tree and do web surfing.
i don't have any idea if it is orgainsed comprehensively in one place.
you serach in your source tree where the address range containing 0xf4axxxxxxhas been
ioremapped.
on some plateform like SPARC there is "vitual io" there you might not need to ioremap
sort of interface for the address range in that "virtual io window" as there is a entry built already for virtual --> physical ...anybody should correct me if i am wrong here..
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-14 6:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 11:47 "Kernel logical address" vs "Physical" Goddeeris Frederic
2001-09-14 6:49 ` ashish anand [this message]
2001-09-14 18:26 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 12:13 Goddeeris Frederic
2001-09-14 10:52 Goddeeris Frederic
2001-09-14 6:06 ` ashish anand
2001-09-14 8:44 Goddeeris Frederic
2001-09-14 4:50 ` ashish anand
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=3BA1A87A.63F07742@india.infogain.com \
--to=ashisha@india.infogain.com \
--cc=Frederic.Goddeeris@siemens.atea.be \
--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;
as well as URLs for NNTP newsgroup(s).