From: "Manuel A. McLure" <mmt@unify.com>
To: "'Jeff Garzik'" <jgarzik@mandrakesoft.com>,
Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
Cc: linux-kernel@vger.kernel.org
Subject: RE: Still IRQ routing problems with VIA
Date: Tue, 10 Apr 2001 14:05:18 -0700 [thread overview]
Message-ID: <419E5D46960FD211A2D5006008CAC79902E5C1A6@pcmailsrv1.sac.unify.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
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.
I do have an IRQ for my VGA since the instructions for my card (a Voodoo 5
5500) specifically say an IRQ is needed.
--
Manuel A. McLure - Unify Corp. Technical Support <mmt@unify.com>
Space Ghost: "Hey, what happened to the-?" Moltar: "It's out." SG: "What
about-?" M: "It's fixed." SG: "Eh, good. Good."
[-- Attachment #2: dmesg_pnp_yes.txt.gz --]
[-- Type: application/octet-stream, Size: 4031 bytes --]
next reply other threads:[~2001-04-10 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 21:05 Manuel A. McLure [this message]
2001-04-10 21:11 ` Still IRQ routing problems with VIA Jeff Garzik
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=419E5D46960FD211A2D5006008CAC79902E5C1A6@pcmailsrv1.sac.unify.com \
--to=mmt@unify.com \
--cc=Axel.Thimm@physik.fu-berlin.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/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).