public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Manuel A. McLure" <mmt@unify.com>
Cc: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Still IRQ routing problems with VIA
Date: Tue, 10 Apr 2001 17:11:42 -0400	[thread overview]
Message-ID: <3AD3770E.8AA6D989@mandrakesoft.com> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C1A6@pcmailsrv1.sac.unify.com>

"Manuel A. McLure" wrote:
> Jeff Garzik said...
> > Changing '#undef DEBUG' to '#define DEBUG 1' in
> > arch/i386/kernel/pci-i386.h is also very helpful.  Can you guys do so,
> > and post the 'dmesg -s 16384' results to lkml?  This includes the same
> > information as dump_pirq, as well as some additional information.
> 
> Here's my dmesg output - I tried with both PNP: Yes and PNP: No and the
> dmesg outputs were exactly the same modulo a Hz or two in the processor
> speed detection.

Thanks.  I'm building a database of these.  There is definitely an issue
with Via and interrupt routing.  Hopefully I can collate this data soon
and figure out what's going on.  I need to find some Via hardware for
myself, too, since I only have an old Via-based laptop which works 100%
;-)


> I do have an IRQ for my VGA since the instructions for my card (a Voodoo 5
> 5500) specifically say an IRQ is needed.

I wonder though... In my mind this is a driver not hardware issue.  If
the XFree86 and/or Linux console driver do not use the IRQ, you need not
have BIOS assign one.  If you are feeling dangerous, try turning the VGA
IRQ assignment off in BIOS and see if things melt/explode/kick ass.

Regards,

	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:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 21:05 Still IRQ routing problems with VIA Manuel A. McLure
2001-04-10 21:11 ` Jeff Garzik [this message]
2001-04-11 19:56   ` Axel Thimm
  -- strict thread matches above, loose matches on Subject: below --
2001-04-10 21:24 Manuel A. McLure
2001-04-10 21:36 ` Jeff Garzik
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=3AD3770E.8AA6D989@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=Axel.Thimm@physik.fu-berlin.de \
    --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