From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix NR_IRQS when no IO apic
Date: Sun, 27 Jan 2002 19:42:06 -0500 [thread overview]
Message-ID: <3C549E5E.4ACA093D@mandrakesoft.com> (raw)
In-Reply-To: <3C549AEC.D79A95FC@didntduck.org>
Brian Gerst wrote:
>
> 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.
> +#ifdef CONFIG_X86_IO_APIC
> #define NR_IRQS 224
> +#else
> +#define NR_IRQS 16
> +#endif
What about when ioapic is configured but not present?
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-01-28 0:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 0:27 [PATCH] Fix NR_IRQS when no IO apic Brian Gerst
2002-01-28 0:42 ` Jeff Garzik [this message]
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=3C549E5E.4ACA093D@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=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