linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64
Date: Mon, 14 May 2007 17:04:02 +0200	[thread overview]
Message-ID: <850bd1e3d0b6c5e23a2fe43154591fd9@kernel.crashing.org> (raw)
In-Reply-To: <200705141637.19572.arnd@arndb.de>

> Do you think it's ok to not treat the range between 64k and 1M special?
> There might be ISA drivers that expect devices in there.

ISA I/O space is 16-bit addressing only.

> Maybe we should
> start PHB_IO_BASE after a 1M guard area where nothing is mapped.

This can cause problems, many PCI bridges and devices
don't decode all 32 bits of the legacy I/O address space.

> Where should Olof's PCMCIA space go? The ISA or the PHB range?

It uses the legacy IDE I/O addresses, so it needs to
go to the 64kB space.  It isn't ISA though.


Segher

  reply	other threads:[~2007-05-14 15:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  7:53 [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64 Benjamin Herrenschmidt
2007-05-14  7:59 ` Benjamin Herrenschmidt
2007-05-14  8:03 ` Benjamin Herrenschmidt
2007-05-14  9:18 ` Benjamin Herrenschmidt
2007-05-14 13:50 ` Segher Boessenkool
2007-05-14 20:53   ` Benjamin Herrenschmidt
2007-05-15  0:17   ` Paul Mackerras
2007-05-15  4:33     ` Segher Boessenkool
2007-05-15  6:04       ` Benjamin Herrenschmidt
2007-05-14 14:37 ` Arnd Bergmann
2007-05-14 15:04   ` Segher Boessenkool [this message]
2007-05-14 23:56     ` Arnd Bergmann
2007-05-15  0:05       ` Olof Johansson
2007-05-14 20:59   ` Benjamin Herrenschmidt
2007-05-14 23:39     ` Arnd Bergmann
2007-05-15  0:06       ` Benjamin Herrenschmidt
2007-05-15 10:56 ` Christoph Hellwig
2007-05-15 20:42   ` Benjamin Herrenschmidt

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=850bd1e3d0b6c5e23a2fe43154591fd9@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=anton@samba.org \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).