From: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Paul Ionescu <i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: IBM T41 + ACPI + APIC
Date: Thu, 12 Aug 2004 13:00:50 -0400 [thread overview]
Message-ID: <411BA242.6010103@optonline.net> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A8470726A996-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Grover, Andrew wrote:
> You need an IOAPIC. The local APIC is basically just the part of the CPU
> that receives messages from the IOAPIC, if present.
By the way, it is a bad idea to use front-side-bus interrupt delivery on
some (all?) Intel mobile processors/chipsets. This prevents entering C3,
if I remember correctly. The real details are in the i850-M databook...
Does turning on IOAPIC+local APIC enable FSB-interrupt mode in Linux?
What about also turning on message-signalled interrupts? Seems we use
the local-apic instead of the IO(x)APIC for MSI.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-12 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 16:50 IBM T41 + ACPI + APIC Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470726A996-sBd4vmA9Se6krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-12 17:00 ` Nathan Bryant [this message]
[not found] ` <411BA242.6010103-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-08-12 19:56 ` Frank Mehnert
-- strict thread matches above, loose matches on Subject: below --
2004-08-12 12:02 Paul Ionescu
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=411BA242.6010103@optonline.net \
--to=nbryant-p32f3xycuykqczcgjluoxw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.