From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
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: Tue, 28 Jan 2003 01:17:10 +0300 [thread overview]
Message-ID: <20030128011710.A638@localhost.park.msu.ru> (raw)
In-Reply-To: <1043690104.2756.42.camel@zion.wanadoo.fr>; from benh@kernel.crashing.org on Mon, Jan 27, 2003 at 06:55:04PM +0100
On Mon, Jan 27, 2003 at 06:55:04PM +0100, Benjamin Herrenschmidt wrote:
> Well, your example clearly limits us to one IO space for VGA, which
> might not be what we want. The problem also exist for some fbdev drivers
> which might need to tap the VGA IOs of a given PCI card (thus getting
> access to the "legacy" IOs of the bus the card is on).
You are right, I've already realized that. :-)
The struct pci_bus * arg to legacy_ioport_remap (maybe better
pci_legacy_ioport_remap) is really good idea, and it's perfectly
ok to pass NULL in the vgacon case - we are limited to only one
VGA console anyway.
After the PCI setup is done, pci_legacy_ioport_remap(pbus, &legacy_resource)
would solve any problem I can think of, including multiple ISA bridges.
Ivan.
next prev parent reply other threads:[~2003-01-27 22:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-26 15:13 [patch 2.5] VGA IO on systems with multiple PCI IO domains 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 [this message]
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
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=20030128011710.A638@localhost.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