linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: [RFC/PATCH] powerpc: Rewrite IO allocation & mapping on powerpc64
Date: Tue, 15 May 2007 06:33:51 +0200	[thread overview]
Message-ID: <66b16b11858147b8790b70416fd3833a@kernel.crashing.org> (raw)
In-Reply-To: <17992.64515.797925.855510@cargo.ozlabs.ibm.com>

>> This is wrong -- there are systems with ISA that
>> also have PCI devices that require 16-bit legacy
>> I/O windows (e.g., systems with the AMD8111 chip,
>> like Maple).
>
> If they are PCI devices and their drivers use a pci_dev's resources
> to get to the device's I/O resources, then they are fine.
>
> The only reason for reserving the low 64k is to cater for drivers that
> use a hard-coded port number, e.g. video drivers using the VGA port
> numbers.  We have been gradually getting rid of the hard coded port
> numbers in drivers but I don't think they're all gone yet.

Yes, I misunderstood (that teaches me for reading the
patch description only, not the patch itself :-) ).

Ben, can we have a config option to _not_ create a
mapping for the legacy hardcoded stuff, even if there
is an "isa" device node?  Some platforms do not need
it or want it, and it can help find the remaining
drivers that do this x86 nastiness.


Segher

  reply	other threads:[~2007-05-15  4:46 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 [this message]
2007-05-15  6:04       ` Benjamin Herrenschmidt
2007-05-14 14:37 ` Arnd Bergmann
2007-05-14 15:04   ` Segher Boessenkool
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=66b16b11858147b8790b70416fd3833a@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=anton@samba.org \
    --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).