From: Russell King <rmk@arm.linux.org.uk>
To: jgarzik@mandrakesoft.com (Jeff Garzik)
Cc: linux-kernel@vger.kernel.org, mj@suse.cz
Subject: Re: VGA PCI IO port reservations
Date: Fri, 17 Nov 2000 16:58:51 +0000 (GMT) [thread overview]
Message-ID: <200011171658.QAA01331@raistlin.arm.linux.org.uk> (raw)
In-Reply-To: <3A15623E.5F21E230@mandrakesoft.com> from "Jeff Garzik" at Nov 17, 2000 11:52:14 AM
Jeff Garzik writes:
> Russell King wrote:
> > Jeff Garzik writes:
> > > > For example, S3 cards typically use:
> > > >
> > > > 0x0102, 0x42e8, 0x46e8, 0x4ae8, 0x8180 - 0x8200, 0x82e8, 0x86e8,
> > > > 0x8ae8, 0x8ee8, 0x92e8, 0x96e8, 0x9ae8, 0x9ee8, 0xa2e8, 0xa6e8,
> > > > 0xaae8, 0xaee8, 0xb2e8, 0xb6e8, 0xbae8, 0xbee8, 0xe2e8,
> > > > 0xff00 - 0xff44
>
> If XFree86 not fbdev is using the hardware, you can always have a stub
> driver that does nothing but reserve the ports. Remember, too, that the
> ports claimed depend on register settings in the video card and PCI
> config space..
I wish. Unfortunately, ones of this nature tend to be rather fixed. No amount
of config space twiddling will move them. However, as someone else pointed out,
x86 gets around this problem by only allowing IO ports to be allocated in the
(addr & 0x0300) == 0 range, thereby avoiding the problem.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King rmk@arm.linux.org.uk --- ---
| | | | http://www.arm.linux.org.uk/personal/aboutme.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-17 17:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 16:20 VGA PCI IO port reservations Russell King
2000-11-17 16:36 ` Jeff Garzik
2000-11-17 16:46 ` Russell King
2000-11-17 16:52 ` Jeff Garzik
2000-11-17 16:58 ` Russell King [this message]
2000-11-17 17:03 ` Jeff Garzik
2000-11-17 17:11 ` Russell King
2000-11-17 21:43 ` Matthew Kirkwood
2000-11-17 22:02 ` H. Peter Anvin
2000-11-18 17:41 ` About IOs, ISA, PCI, and life (WAS: VGA PCI IO port...) Benjamin Herrenschmidt
2000-11-17 17:13 ` VGA PCI IO port reservations Richard B. Johnson
2000-11-17 17:20 ` Russell King
2000-11-17 17:30 ` Alan Cox
2000-11-17 18:06 ` Richard B. Johnson
2000-11-17 19:52 ` Russell King
2000-11-17 19:59 ` Richard B. Johnson
2000-11-17 20:02 ` Russell King
2000-11-17 20:27 ` Richard B. Johnson
2000-11-18 1:20 ` Olivier Galibert
2000-11-18 2:10 ` H. Peter Anvin
2000-11-18 17:02 ` Alan Cox
2000-11-27 22:10 ` Kai Henningsen
2000-11-17 21:35 ` Marcus Sundberg
2000-11-17 20:13 ` H. Peter Anvin
2000-11-17 20:31 ` Richard B. Johnson
2000-11-17 16:47 ` Brian Gerst
2000-11-17 16:56 ` Russell King
2000-11-17 17:00 ` Jeff Garzik
2000-11-17 18:29 ` H. Peter Anvin
2000-11-17 18:27 ` H. Peter Anvin
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=200011171658.QAA01331@raistlin.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mj@suse.cz \
/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