From: "Brown, Len" <len.brown@intel.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: "Stian Jordet" <liste@jordet.nu>, <linux-kernel@vger.kernel.org>
Subject: RE: [SOLVED] RE: 2.6.0-test3 latest bk hangs when enabling IO-APIC
Date: Mon, 18 Aug 2003 23:17:01 -0400 [thread overview]
Message-ID: <BF1FE1855350A0479097B3A0D2A80EE009FC7B@hdsmsx402.hd.intel.com> (raw)
> So... concrete suggestions? Overall, IMO, move everything under
> CONFIG_ACPI, or, make CONFIG_ACPI_BOOT a _peer_ option, whose
> selection
> or lackthereof doesn't affect CONFIG_ACPI visibility at all.
Simply re-naming CONFIG_ACPI_HT to be CONFIG_ACPI_BOOT might help, as it
would be more clear that it is necessary for the rest of ACPI. However,
it may not be obvious that it provides the minimal config to enable HT.
Re: peers
Unfortunately ACPI doesn't work so well if CONFIG_ACPI_BOOT is left out.
Yes, it's conceivable, but I spent several hours tinkering with it in
search of a "noht" build option, but ditched it b/c it seemed like a
build option very few would use.
Re: CONFIG_ACPI is the the master switch, and all other ACPI options
subservient...
If implemented literally, this is sort of a pain, as CONFIG_ACPI appears
all over the code. However, a dummy config master ACPI config option
could be used to enable the menu that contains all the rest of ACPI...
-Len
next reply other threads:[~2003-08-19 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 3:17 Brown, Len [this message]
2003-08-19 12:54 ` [SOLVED] RE: 2.6.0-test3 latest bk hangs when enabling IO-APIC Stian Jordet
2003-08-19 15:26 ` Jeff Garzik
2003-08-19 15:44 ` Stian Jordet
-- strict thread matches above, loose matches on Subject: below --
2003-08-19 1:15 Brown, Len
2003-08-19 1:57 ` Jeff Garzik
2003-08-19 7:22 ` Stian Jordet
2003-08-22 2:11 ` Mark W. Alexander
2003-08-18 17:53 Brown, Len
2003-08-18 19:23 ` Stian Jordet
2003-08-18 20:06 ` Stian Jordet
2003-08-18 23:06 ` [SOLVED] " Stian Jordet
2003-08-18 23:12 ` Stian Jordet
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=BF1FE1855350A0479097B3A0D2A80EE009FC7B@hdsmsx402.hd.intel.com \
--to=len.brown@intel.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liste@jordet.nu \
/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;
as well as URLs for NNTP newsgroup(s).