public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Brian Gerst <bgerst@didntduck.org>,
	linux-kernel@vger.kernel.org, mj@suse.cz
Subject: Re: VGA PCI IO port reservations
Date: Fri, 17 Nov 2000 12:00:18 -0500	[thread overview]
Message-ID: <3A156422.7D1D3DBD@mandrakesoft.com> (raw)
In-Reply-To: <200011171656.QAA01320@raistlin.arm.linux.org.uk>

Russell King wrote:
> 
> 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.

Oh yeah, if you are writing for S3 specifically, you can do 100% MMIO,
and simply turn off all I/O decoding.  Check out Keith Packard's
kdrive/s3trio in the XFree86 tree...

	Jeff


-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
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/

  reply	other threads:[~2000-11-17 17:30 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
2000-11-17 17:00     ` Jeff Garzik [this message]
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=3A156422.7D1D3DBD@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@suse.cz \
    --cc=rmk@arm.linux.org.uk \
    /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