linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Manuel A. McLure" <mmt@unify.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Still IRQ routing problems with VIA
Date: Tue, 10 Apr 2001 17:36:13 -0400	[thread overview]
Message-ID: <3AD37CCD.DB0CCCD@mandrakesoft.com> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A7@pcmailsrv1.sac.unify.com>

"Manuel A. McLure" wrote:
> I'd do that if this wasn't also my Windows 98 gaming machine - I'm supposing
> that the Windows drivers do use the IRQ even if XFree86/Linux doesn't. I
> dunno if Windows is smart enough to assign an IRQ even if the BIOS doesn't.
> Anyway, things are working now (specially since the last tulip patches) and
> I like it that way :-)

Well, as the old saying goes, "if it ain't broke, don't fix it."

Theoretically, with PNP OS enabled, the driver will assign VGA an IRQ if
it needs one, under both Windows and Linux.

	Jeff


-- 
Jeff Garzik       | Sam: "Mind if I drive?"
Building 1024     | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft      |       and shrieking like a cheerleader."

  reply	other threads:[~2001-04-10 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 21:24 Still IRQ routing problems with VIA Manuel A. McLure
2001-04-10 21:36 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-10 21:05 Manuel A. McLure
2001-04-10 21:11 ` Jeff Garzik
2001-04-11 19:56   ` Axel Thimm
2001-04-10 17:52 Manuel A. McLure
2001-04-10 18:01 ` Jeff Garzik
2001-04-10 16:51   ` Still IRQ routing problems with VIA (was: VIA KT133 chipset P CI crazyness...) Manuel A. McLure
2001-04-10 17:31     ` Still IRQ routing problems with VIA Axel Thimm
2001-04-10 17:38       ` Jeff Garzik
2001-04-10 19:16         ` Axel Thimm
2001-04-11 15:13 ` Pierre Etchemaite

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=3AD37CCD.DB0CCCD@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmt@unify.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;
as well as URLs for NNTP newsgroup(s).