From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: APIC options 2.4.21 kernel + patch
Date: Tue, 1 Jul 2003 10:00:34 +0200 [thread overview]
Message-ID: <20030701080034.GA873@enigma.daemon.sh> (raw)
In-Reply-To: <20030701052006.GB2242-MHIYrZpDPrNWk0Htik3J/w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
hello there...
* Emma Jane Hogbin <emmajane-MHIYrZpDPrNWk0Htik3J/w@public.gmane.org> [2003-07-01 09:16 +0200]:
>
> http://xtrinsic.com/geek/articles/acpi.phtml
>
> Here is a copy of the email I received which outlines the problem behind
> the question:
> http://sourceforge.net/mailarchive/forum.php?thread_id=2668793&forum_id=7803
>
> My question is this: Does the CONFIG_X86_UP_APIC module need to be set to
> "Y" for the 2.4.21 kernel + latest ACPI patch to work?
>
> I've found the following APIC options in the 2.4.20 kernel:
> CONFIG_X86_GOOD_APIC=y
> # CONFIG_X86_UP_APIC is not set
> # CONFIG_X86_UP_IOAPIC is not set
>
> The reader who emailed me said that he had to enable the second option in
> order to get the 2.4.21 kernel + patch to work. Will this be true for all
> hardware configurations 2.4.21?
i cannot second that, at least concerning kernel configuration. when i
disable the APIC-stuff i can still select ACPI in my configuration.
also drivers/acpi/Config.in does not seem to depend on settings for APIC
except for CPU enumeration (CONFIG_X86_LOCAL_APIC which is enabled
automatically by CONFIG_X86_UP_APIC).
grepping the kernel sources for UP_APIC does not seem to alter anything
within the ACPI codebase. though CONFIG_X86_UP_IOAPIC automatically enables
CONFIG_X86_IO_APIC which alters ACPIs behaviour (compilation) quite a bit.
this is 2.4.21 + acpi20030619 (+ swsusp-1.0pre14 + laptopmode + bootsplash +
dsdtinitrd).
though i am neither a kernel developer nor an acpi developer and i could
be damn wrong. :)
cheers,
sebastian
--
::: sebastian henschel
::: kodeaffe
::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-01 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 5:20 APIC options 2.4.21 kernel + patch Emma Jane Hogbin
[not found] ` <20030701052006.GB2242-MHIYrZpDPrNWk0Htik3J/w@public.gmane.org>
2003-07-01 8:00 ` Sebastian Henschel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 2:34 Brown, Len
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=20030701080034.GA873@enigma.daemon.sh \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox