From: Brian Gerst <bgerst@didntduck.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [PATCH] Fix NR_IRQS when no IO apic
Date: Sun, 27 Jan 2002 19:27:24 -0500 [thread overview]
Message-ID: <3C549AEC.D79A95FC@didntduck.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 245 bytes --]
NR_IRQS should be 16 when the IO apic is not configured, as the 8259 PIC
cannot generate any more interrupts. It also fixes a bug where the IDT
gets populated with random addresses, since only 16 entry stubs are
created.
--
Brian Gerst
[-- Attachment #2: nrirqs-1 --]
[-- Type: text/plain, Size: 483 bytes --]
diff -urN linux-2.5.3-pre5/include/asm-i386/irq.h linux/include/asm-i386/irq.h
--- linux-2.5.3-pre5/include/asm-i386/irq.h Fri Jan 25 02:25:47 2002
+++ linux/include/asm-i386/irq.h Fri Jan 25 11:30:44 2002
@@ -23,7 +23,11 @@
* Since vectors 0x00-0x1f are used/reserved for the CPU,
* the usable vector space is 0x20-0xff (224 vectors)
*/
+#ifdef CONFIG_X86_IO_APIC
#define NR_IRQS 224
+#else
+#define NR_IRQS 16
+#endif
static __inline__ int irq_cannonicalize(int irq)
{
next reply other threads:[~2002-01-28 0:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 0:27 Brian Gerst [this message]
2002-01-28 0:42 ` [PATCH] Fix NR_IRQS when no IO apic Jeff Garzik
2002-01-28 0:51 ` Brian Gerst
2002-01-28 1:07 ` Robert Love
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=3C549AEC.D79A95FC@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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