linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: bh40@calva.net
Cc: geert@linux-m68k.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: dual head r128
Date: Fri, 13 Oct 2000 23:47:47 +0200 (CEST)	[thread overview]
Message-ID: <200010132147.XAA00867@piglet.grunz.lu> (raw)
In-Reply-To: <19340907150812.9049@192.168.1.10>


> Ok, If I follow you correctly, that mean that if we have, for example,
> bus 1 set to 0x10000-0x1ffff, ioportremap() would return, for an address
> in this range, the address + bus_io_base - 0x10000. At least on Macs,
> AFAIK, we have only 64k or 128k of IOs available.

No, the regions are larger. Apple's doc talks about '23 bits of IO
space', which is 8M, at least for the first-generation bridges (bandit,
that is).

Anyway, the best way to find out the size of this region (unless you can
read it from the bridge) is to look at the OF device tree, and the
bridge's region properties.

Cheers

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-10-13 21:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` dual head r128 Benjamin Herrenschmidt
2000-10-13 21:47   ` Michel Lanners [this message]
2000-10-14 10:13     ` Benjamin Herrenschmidt
2000-10-14 10:21   ` Geert Uytterhoeven
     [not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
     [not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
2000-10-12 16:25 Hendricks, Kevin
  -- strict thread matches above, loose matches on Subject: below --
2000-10-12 14:30 Hendricks, Kevin
2000-10-12 16:11 ` Kostas Gewrgiou
2000-10-12 17:22   ` Michel Dänzer
2000-10-12 17:44     ` Kostas Gewrgiou
2000-10-12 21:25       ` Michel Dänzer
2000-10-13 15:26         ` Kostas Gewrgiou
2000-10-13 16:21       ` Geert Uytterhoeven
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-11 18:17 Josh Huber
2000-10-11 18:43 ` Michel Dänzer
2000-10-11 18:52   ` Josh Huber
2000-10-11 19:04     ` Tom Rini
2000-10-11 19:09     ` Michel Dänzer
2000-10-11 19:26       ` Josh Huber
2000-10-11 22:48         ` Michel Dänzer
2000-10-13 17:16           ` Josh Huber
2000-10-12 13:09     ` Kostas Gewrgiou
2000-10-12 15:13       ` Benjamin Herrenschmidt
2000-10-12 15:49         ` Gabriel Paubert
2000-10-12 16:40           ` David Edelsohn
2000-10-17  0:12           ` Paul Mackerras
2000-10-17  5:56             ` Michel Lanners
2000-10-17 10:41             ` Benjamin Herrenschmidt
2000-10-17 13:45               ` Geert Uytterhoeven
2000-10-17 17:17                 ` Benjamin Herrenschmidt
2000-10-12 16:44         ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert

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=200010132147.XAA00867@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=bh40@calva.net \
    --cc=geert@linux-m68k.org \
    --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;
as well as URLs for NNTP newsgroup(s).