From: "Brown, Len" <len.brown@intel.com>
To: "Sérgio Monteiro Basto" <sergiomb@netcabo.pt>,
"Marcelo Tosatti" <marcelo@conectiva.com.br>
Cc: "Jeff Garzik" <jgarzik@pobox.com>,
"Grover, Andrew" <andrew.grover@intel.com>,
"J.A. Magallon" <jamagallon@able.es>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
<acpi-devel@sourceforge.net>, "Patrick Mochel" <mochel@osdl.org>
Subject: RE: [ACPI] RE: [patch] 2.4.x ACPI updates
Date: Wed, 20 Aug 2003 19:55:13 -0400 [thread overview]
Message-ID: <BF1FE1855350A0479097B3A0D2A80EE009FC96@hdsmsx402.hd.intel.com> (raw)
Yeah, broke this in 2.6 also -- apparently neglected to test that change w/o CONFIG_SMP...
Patrick suggested a cleaner way to do this code using fewer #ifdefs, so I'll try that out this evening. Until that arrives, you can just nuke that line and the "noapic" flag will revert to being broken in ACPI mode like it was before this week.
Thanks,
-Len
===== arch/i386/kernel/setup.c 1.91 vs edited =====
--- 1.91/arch/i386/kernel/setup.c Sat Aug 16 00:28:34 2003
+++ edited/arch/i386/kernel/setup.c Wed Aug 20 19:48:21 2003
@@ -545,7 +545,7 @@
/* disable IO-APIC */
else if (!memcmp(from, "noapic", 6)) {
- skip_ioapic_setup = 1;
+// skip_ioapic_setup = 1;
}
#endif
next reply other threads:[~2003-08-20 23:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 23:55 Brown, Len [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 21:05 [patch] 2.4.x ACPI updates Brown, Len
2003-08-23 21:30 ` Marcelo Tosatti
2003-08-23 22:33 ` [ACPI] " Karol Kozimor
2003-09-02 14:37 ` Pavel Machek
2003-09-08 13:29 ` Karol Kozimor
2003-09-09 7:32 ` Karol Kozimor
2003-08-24 10:36 ` Eric Valette
2003-08-20 0:04 Brown, Len
2003-08-20 18:15 ` Marcelo Tosatti
2003-08-20 23:06 ` [ACPI] " Sérgio Monteiro Basto
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=BF1FE1855350A0479097B3A0D2A80EE009FC96@hdsmsx402.hd.intel.com \
--to=len.brown@intel.com \
--cc=acpi-devel@sourceforge.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.com \
--cc=jamagallon@able.es \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mochel@osdl.org \
--cc=sergiomb@netcabo.pt \
/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).