From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
arjanv@redhat.com, "Axel Thimm" <Axel.Thimm@physik.fu-berlin.de>,
"Manuel A. McLure" <mmt@unify.com>,
"Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>,
"ARND BERGMANN" <std7652@et.FH-Osnabrueck.DE>,
"Dunlap Randy" <randy.dunlap@intel.com>,
"Martin Diehl" <mdiehlcs@compuserve.de>,
"Adrian Cox" <adrian@humboldt.co.uk>,
"Capricelli Thomas" <orzel@kde.org>,
"Ian Bicking" <ianb@colorstudy.com>,
"John R Lenton" <john@grulic.org.ar>
Subject: Re: PATCH 2.4.5.1: Fix Via interrupt routing issues
Date: Sun, 13 May 2001 14:45:42 -0400 [thread overview]
Message-ID: <3AFED656.92362303@mandrakesoft.com> (raw)
In-Reply-To: <E14z0l8-0006oS-00@the-village.bc.nu>
Alan Cox wrote:
>
> > +/* we will likely need a better ifdef, something like
> > + * ifdef CONFIG_EXTERNAL_APIC
> > + */
> > +#ifdef CONFIG_X86_IO_APIC
>
> I disagree. The IO-APIC is the chipset APIC. It is distinct from the APIC
> on the processors.
Disagree with which part? The fix, or likely needing a better ifdef?
>From the point of view of the Via southbridge chip, IO-APIC is
external... The comment above the ifdef was more along the lines of,
"Via on PPC (OpenPIC?) might need this too, not just io-apic"
--
Jeff Garzik | Game called on account of naked chick
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-13 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 17:28 PATCH 2.4.5.1: Fix Via interrupt routing issues Jeff Garzik
2001-05-13 18:38 ` Alan Cox
2001-05-13 18:45 ` Jeff Garzik [this message]
2001-05-13 18:47 ` Alan Cox
2001-05-14 15:21 ` Axel Thimm
2001-05-14 16:16 ` Jeff Garzik
2001-05-14 19:05 ` Axel Thimm
2001-05-14 19:14 ` Axel Thimm
2001-05-14 17:07 ` John R Lenton
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=3AFED656.92362303@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=Axel.Thimm@physik.fu-berlin.de \
--cc=adrian@humboldt.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=ianb@colorstudy.com \
--cc=john@grulic.org.ar \
--cc=linux-kernel@vger.kernel.org \
--cc=mdiehlcs@compuserve.de \
--cc=mmt@unify.com \
--cc=moffe@amagerkollegiet.dk \
--cc=orzel@kde.org \
--cc=randy.dunlap@intel.com \
--cc=std7652@et.FH-Osnabrueck.DE \
/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