LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: costabel@wanadoo.fr
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Accessing IO space via resources
Date: Sun, 25 Jun 2000 09:39:30 +0200 (CEST)	[thread overview]
Message-ID: <200006250739.JAA00730@piglet.grunz.lu> (raw)
In-Reply-To: <395527BA.3E61D7BC@wanadoo.fr>


Hi all,

On  24 Jun, this message from Martin Costabel echoed through cyberspace:
>> After investigating this, it turns out that early in the boot process,
>> before the mm system is up, ioremap returns virt == phys for
>> addresses >= ioremap_base. ioremap_base got changed from 0xf8000000 to
>> 0xf0000000 in recent kernels. Anybody kow why this got changed?
>
> Browsing bk diffs (BTW, it's rather the other way round),

Oooppss.. of course.

> this looks
> very much like a typo. Paulus, on 06/09/2000, cleaning up too
> thoroughly?

Might be...

But on the other hand, what's the reason for having the ioremap_base
limit other than for the sake of mapping 1:1 above it?

If the reason is to map 1:1, no luck... there's hardly anything besides
ROM above 0xf8000000 on PowerMacs. In that case, and supposing it was
moved to make more room below it, it can be moved to 0xffffffff anyway..

Thanks

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


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

      reply	other threads:[~2000-06-25  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-23 12:24 Accessing IO space via resources Michel Lanners
2000-06-24  6:32 ` Michel Lanners
2000-06-24 21:27   ` Martin Costabel
2000-06-25  7:39     ` Michel Lanners [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=200006250739.JAA00730@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=costabel@wanadoo.fr \
    --cc=linuxppc-dev@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