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: linux-kernel@vger.kernel.org, mj@suse.cz
Subject: Re: VGA PCI IO port reservations
Date: Fri, 17 Nov 2000 11:52:14 -0500	[thread overview]
Message-ID: <3A15623E.5F21E230@mandrakesoft.com> (raw)
In-Reply-To: <200011171646.QAA01224@raistlin.arm.linux.org.uk>

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
>       ^^^^ PCI IO addresses

Oops, you're right :)


> If the driver isn't loaded, the port is still used by the hardware.  Therefore,
> it should be reserved independent of whether we have the driver loaded/in kernel
> or not.

That logic doesn't work.  If you believe that, then the core kernel
needs to be doing 100% of the request_region calls, right at bootup...

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..

	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:23 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 [this message]
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
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=3A15623E.5F21E230@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --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