public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: root@chaos.analogic.com
Cc: jgarzik@mandrakesoft.com (Jeff Garzik),
	linux-kernel@vger.kernel.org, mj@suse.cz
Subject: Re: VGA PCI IO port reservations
Date: Fri, 17 Nov 2000 17:20:28 +0000 (GMT)	[thread overview]
Message-ID: <200011171720.RAA01403@raistlin.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.3.95.1001117114858.19946A-100000@chaos.analogic.com> from "Richard B. Johnson" at Nov 17, 2000 12:13:14 PM

Richard B. Johnson writes:
> This can't be.

Richard,  before I read any further, I suggest that you get some
documentation on a few PCI VGA cards and read up on the register
addresses.  You may want to change your assumptions about what can and
can't be. ;)

And I can definitely say that if you don't allow access to these "extended"
VGA ports, BIOSes either enter infinite loops or else terminate without
initialising the card.  Trust me; I've been successfully running various
PCI VGA card BIOSes under an x86 emulator on an ARM machine for the past
few months.
   _____
  |_____| ------------------------------------------------- ---+---+-
  |   |         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/

  reply	other threads:[~2000-11-17 17:51 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 [this message]
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=200011171720.RAA01403@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 \
    --cc=root@chaos.analogic.com \
    /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