From: Russell King <rmk@arm.linux.org.uk>
To: bgerst@didntduck.org (Brian Gerst)
Cc: linux-kernel@vger.kernel.org, mj@suse.cz
Subject: Re: VGA PCI IO port reservations
Date: Fri, 17 Nov 2000 16:56:47 +0000 (GMT) [thread overview]
Message-ID: <200011171656.QAA01320@raistlin.arm.linux.org.uk> (raw)
In-Reply-To: <3A156116.65CDBBE9@didntduck.org> from "Brian Gerst" at Nov 17, 2000 11:47:18 AM
Brian Gerst writes:
> This is an artifact from the ISA 10-bit IO bus. Many ISA cards do not
> decode all 16 address bits so you get aliases of the 0x100-0x3ff region
> throughout IO space. PCI cards should only use the first 256 ports of
> any 1k block to avoid aliases unless they claim the base alias. For
> example, all the xxe8 addresses for the S3 are aliases of 0x02e8 to an
> ISA card. Video cards are an exception to the general rule because they
> have to support all the legacy VGA crap.
No. All xxe8 addresses access specific registers. For example:
0x9ea8 is the drawing command
0xa2e8 is the background colour register
0xa6e8 is the foreground colour register
So, as you see they aren't aliases.
> /*
> * We need to avoid collisions with `mirrored' VGA ports
> * and other strange ISA hardware, so we always want the
> * addresses to be allocated in the 0x000-0x0ff region
> * modulo 0x400.
> *
> * Why? Because some silly external IO cards only decode
> * the low 10 bits of the IO address. The 0x00-0xff region
> * is reserved for motherboard devices that decode all 16
> * bits, so it's ok to allocate at, say, 0x2800-0x28ff,
> * but we want to try to avoid allocating at 0x2900-0x2bff
> * which might have be mirrored at 0x0100-0x03ff..
> */
Ah ha, I'll nick that for the ARM stuff then. Thanks for pointing it out.
_____
|_____| ------------------------------------------------- ---+---+-
| | 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:27 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
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 [this message]
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=200011171656.QAA01320@raistlin.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=bgerst@didntduck.org \
--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