From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Martin Mares <mj@ucw.cz>, Richard Henderson <rth@twiddle.net>,
"Wiedemeier, Jeff" <Jeff.Wiedemeier@hp.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.5] VGA IO on systems with multiple PCI IO domains
Date: Tue, 28 Jan 2003 13:24:06 +0300 [thread overview]
Message-ID: <20030128132406.A9195@jurassic.park.msu.ru> (raw)
In-Reply-To: <Pine.GSO.4.21.0301281030590.9269-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Tue, Jan 28, 2003 at 10:32:53AM +0100
On Tue, Jan 28, 2003 at 10:32:53AM +0100, Geert Uytterhoeven wrote:
> BTW, we still need a separate isa_request_mem_region(), since right now we
> cannot simply call request_mem_region(0xa0000, 0x10000) to request the VGA
> memory buffer in ISA memory space. On ia32 the plain request_mem_region() is
> OK, but on other archs you need to add the ISA memory space base.
I agree. Currently the VGA_MAP_MEM() hack does the trick in the vgacon.c,
but it would be a lot better to have a generic function.
However, I don't think that "isa_" prefix is good - as Ben pointed out,
legacy IO ranges of PCI devices like VGA, IDE, serial etc. can be
in other IO spaces than the real ISA bus.
What about
int pci_request_legacy_resource(struct pci_bus *bus, struct resource *res)
which would check res->flags and make appropriate decision?
The default in <linux/pci.h> for architectures like ia32 will be
#ifndef __HAVE_ARCH_LEGACY_REMAP
static inline int
pci_request_legacy_resource(struct pci_bus *bus, struct resource *res)
{
struct resource *root = res->flags & IORESOURCE_IO ?
&ioport_resource : &iomem_resource;
return request_resource(root, res);
}
#infdef
This can be overridden in <asm/pci.h>.
Ivan.
next prev parent reply other threads:[~2003-01-28 10:16 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 [this message]
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=20030128132406.A9195@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®