From: Len Brown <len.brown@intel.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: ACPI Developers <acpi-devel@lists.sourceforge.net>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [BKPATCH] ACPI for 2.4
Date: 28 Oct 2004 05:33:21 -0400 [thread overview]
Message-ID: <1098955997.5402.122.camel@d845pe> (raw)
Hi Marcelo, please do a
bk pull bk://linux-acpi.bkbits.net/24-latest-release
thanks,
-Len
ps. a plain patch is also available here:
ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/24-latest-release/acpi-20040326-24-latest-release.diff.gz
This will update the following files:
arch/i386/kernel/apic.c | 6
arch/i386/kernel/dmi_scan.c | 40 ------
arch/i386/kernel/mpparse.c | 2
drivers/acpi/Makefile | 2
drivers/acpi/bus.c | 39 +++++-
drivers/acpi/events/evmisc.c | 2
drivers/acpi/motherboard.c | 159 ++++++++++++++++++++++++++
drivers/acpi/osl.c | 6
drivers/acpi/utilities/utglobal.c | 6
include/acpi/acglobal.h | 37 ++++--
include/acpi/acpi_drivers.h | 3
include/asm-i386/mpspec.h | 1
init/main.c | 6
13 files changed, 246 insertions(+), 63 deletions(-)
through these ChangeSets:
<len.brown@intel.com> (04/10/13 1.1458.1.4)
[ACPI] If BIOS disabled the LAPIC, believe it by default.
"lapic" is available to force enabling the LAPIC
in the event you know more than your BIOS vendor.
http://bugzilla.kernel.org/show_bug.cgi?id=3238
<len.brown@intel.com> (04/08/25 1.1458.1.3)
[ACPI] build fix
<len.brown@intel.com> (04/08/24 1.1458.1.2)
[ACPI] fix build warnings
<len.brown@intel.com> (04/08/24 1.1458.1.1)
[ACPI] Enter ACPI mode earlier
Fixes two common boot failures due to buggy SMM BIOS code
SMP boot crash if SMI_CMD=ACPI written from CPU1
http://bugzilla.kernel.org/show_bug.cgi?id=2941
laptop crash due to LAPIC timer before SMI_CMD=ACPI
http://bugzilla.kernel.org/show_bug.cgi?id=1269
<len.brown@intel.com> (04/08/13 1.1458)
set acpi_gbl_leave_wake_gpes_disabled to FALSE for 2.4
because it would take a backport of big 2.6 changes to make
this code work and 2.4 doesn't support suspend/resume anyway.
<len.brown@intel.com> (04/08/13 1.1457)
[ACPI] boot option fixes from 2.6
"acpi_serialize" "acpi_wake_gpes_always_on" "acpi_osi="
http://bugzilla.kernel.org/show_bug.cgi?id=2534
<len.brown@intel.com> (04/06/24 1.1359.6.29)
[ACPI] reserve IOPORTS for ACPI (David Shaohua Li)
http://bugzilla.kernel.org/show_bug.cgi?id=2641
next reply other threads:[~2004-10-28 9:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 9:33 Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 8:32 [BKPATCH] ACPI for 2.4 Len Brown
2004-11-23 6:34 Len Brown
2004-11-16 19:26 Len Brown
2004-11-09 8:17 Len Brown
2004-06-18 7:32 Len Brown
2004-05-20 6:14 Len Brown
2004-05-06 22:28 Len Brown
2004-04-01 12:24 O.Sezer
2004-04-01 12:57 ` O.Sezer
2004-04-01 10:40 Len Brown
2004-03-27 0:53 Len Brown
2004-03-23 10:43 Len Brown
2004-03-14 6:01 Len Brown
2004-03-06 6:32 Len Brown
2004-02-25 10:01 Len Brown
2004-02-07 9:10 Len Brown
2004-02-08 8:20 ` Willy Tarreau
2004-02-08 9:08 ` Willy Tarreau
2003-11-18 20:58 Len Brown
2003-11-20 11:16 ` Len Brown
2003-11-21 17:49 ` Willy Tarreau
2003-11-21 18:46 ` Willy Tarreau
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=1098955997.5402.122.camel@d845pe \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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