From: Martin Mares <mj@ucw.cz>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: 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: Sun, 26 Jan 2003 22:45:50 +0100 [thread overview]
Message-ID: <20030126214550.GB6873@ucw.cz> (raw)
In-Reply-To: <20030126181326.A799@localhost.park.msu.ru>
Hi!
> But on modern systems (titan and marvel), the firmware supports vga
> on *any* bus. Even worse, marvel doesn't have dedicated "legacy"
> hose at all.
> So we have to decode and fix IO port addresses inside our in/out
> functions, which is awful.
Is the problem really only with VGA? Shouldn't we introduce
isa_(in|out)(b|w) instead and remap the whole legacy I/O space?
Have a nice fortnight
--
Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/
Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth
Don't take life too seriously -- you'll never get out of it alive.
next prev parent reply other threads:[~2003-01-26 21:36 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 [this message]
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
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=20030126214550.GB6873@ucw.cz \
--to=mj@ucw.cz \
--cc=Jeff.Wiedemeier@hp.com \
--cc=geert@linux-m68k.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.