mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Martin Mares <mj@ucw.cz>,
	geert@linux-m68k.org, Richard Henderson <rth@twiddle.net>,
	"Wiedemeier, Jeff" <Jeff.Wiedemeier@hp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2.5] VGA IO on systems with multiple PCI IO domains
Date: Mon, 27 Jan 2003 13:12:42 +0300	[thread overview]
Message-ID: <20030127131242.B2569@jurassic.park.msu.ru> (raw)
In-Reply-To: <1043624458.2755.37.camel@zion.wanadoo.fr>; from benh@kernel.crashing.org on Mon, Jan 27, 2003 at 12:40:59AM +0100

On Mon, Jan 27, 2003 at 12:40:59AM +0100, Benjamin Herrenschmidt wrote:
> We probably need to introduce an equivalent of ioremap for IO space. So
> far, what we have to deal is:
> 
>  - Legacy ISA stuff unrelated to a PCI bus

Well, actually the ISA stuff *is* related to PCI bus on everything
newer than 486 PCs as it's connected to PCI via PCI-to-ISA bridge.
Even worse, I've found that at least two vendors offer PCI-to-ISA
expansion systems (yes, these systems are limited to IO only
on PCs because it clashes with another ISA bus in the same PCI domain),
but this means that one can have multiple ISA busses on alpha, parisc,
sparc64, ppc etc. One ISA bus per PCI IO domain. Shudder...

>  - Legacy devies on a given PCI segment (VGA, serial, IDE, ...)
> 
> What about some kind of ioport_remap() that would take a pci_bus and an
> port range as arguments ? If pci_bus is NULL, that would match a
> "legacy" ISA bus (non-PCI machine or default ISA bus for machines where
> that makes sense).

The problem is that vgacon driver is special - is starts very early,
before PCI subsystem is probed and initialized. So we don't have pci_bus
at this point.

Ivan.

      parent reply	other threads:[~2003-01-27 10:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26 15:13 Ivan Kokshaysky
2003-01-26 21:45 ` Martin Mares
2003-01-26 23:40   ` Benjamin Herrenschmidt
2003-01-27  9:46     ` Martin Mares
2003-01-27 10:40       ` Ivan Kokshaysky
2003-01-27 17:55         ` Benjamin Herrenschmidt
2003-01-27 22:17           ` Ivan Kokshaysky
2003-01-28  9:32             ` Geert Uytterhoeven
2003-01-28 10:24               ` Ivan Kokshaysky
2003-01-28 10:27                 ` Geert Uytterhoeven
2003-01-28 10:40                   ` Ivan Kokshaysky
2003-01-28 17:10                   ` Ivan Kokshaysky
2003-01-28 17:23                     ` Benjamin Herrenschmidt
2003-01-28 17:33                       ` Ivan Kokshaysky
2003-01-29 16:06                       ` Ivan Kokshaysky
2003-01-29 18:15                         ` James Simmons
2003-02-05 11:12                           ` Ivan Kokshaysky
2003-03-12 19:08                         ` Jesse Barnes
2003-01-27 10:12     ` Ivan Kokshaysky [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=20030127131242.B2569@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=Jeff.Wiedemeier@hp.com \
    --cc=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=rth@twiddle.net \
    /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

all inboxes | Powered by JetHome®