From: Jeff Garzik <jgarzik@pobox.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: torvalds@osdl.org, "Grover, Andrew" <andrew.grover@intel.com>,
zwane@linuxpower.ca, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 'noapic' already handled elsewhere
Date: Thu, 21 Aug 2003 17:11:18 -0400 [thread overview]
Message-ID: <3F453576.7020605@pobox.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE009FCA0@hdsmsx402.hd.intel.com>
Brown, Len wrote:
> Jeff,
> This won't work.
> acpi_boot_init() is called from setup_arch(), which is called from
> start_kernel() _before_ parse_options(). Ie. ACPI needs to consume this
> flag before __setup() is invoked.
Thanks for the correction. I'll resend the earlier
s/LOCAL_APIC/IO_APIC/ patch then.
Just found another ACPI bug in 2.6:
> config ACPI_HT
> bool "ACPI Processor Enumeration for HT"
> depends on (X86 && X86_LOCAL_APIC)
> default y
[...]
> config ACPI
> bool "Full ACPI Support"
> depends on !X86_VISWS
> depends on !IA64_HP_SIM
> depends on IA64 || (X86 && ACPI_HT)
So CONFIG_ACPI is not allowed on uniprocessor anymore, _and_ it requires
HyperThreading code? ;-) No wonder CONFIG_ACPI didn't appear for my
uniprocessor Pentium3 'make oldconfig' ;-)
(ACPI requires ACPI_HT, which requires LOCAL_APIC)
Another reason why I was saying that CONFIG_ACPI should be the toplevel
config option (even if CONFIG_ACPI never actually appears in any code,
but only in Kconfig)...
Jeff
next prev parent reply other threads:[~2003-08-21 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 17:09 [PATCH] 'noapic' already handled elsewhere Brown, Len
2003-08-21 21:11 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 21:33 Brown, Len
2003-08-21 16:14 Jeff Garzik
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=3F453576.7020605@pobox.com \
--to=jgarzik@pobox.com \
--cc=andrew.grover@intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zwane@linuxpower.ca \
/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