From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, linux-acpi@vger.kernel.org, lenb@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] X86: Revamp reboot behaviour to match Windows more closely
Date: Thu, 9 Dec 2010 22:38:47 +0000 [thread overview]
Message-ID: <20101209223847.GA24452@srcf.ucam.org> (raw)
In-Reply-To: <4D015914.1040009@zytor.com>
On Thu, Dec 09, 2010 at 02:32:52PM -0800, H. Peter Anvin wrote:
> On 12/09/2010 02:32 PM, Matthew Garrett wrote:
>> On Thu, Dec 09, 2010 at 02:25:05PM -0800, H. Peter Anvin wrote:
>>> When this was discussed before we agreed to use ACPI reboot by default
>>> with an ACPI cutoff date; this doesn't have any such cutoff.
>>
>> Windows doesn't either. Older machines simply won't have the appropriate
>> flag set in their FADT.
>>
>
> Windows doesn't get validated on old hardware.
XP does this, and older hardware predates the version of the ACPI spec
that introduced this flag.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-12-09 22:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 21:46 [PATCH 1/3] X86: Revamp reboot behaviour to match Windows more closely Matthew Garrett
2010-12-09 21:46 ` [PATCH 2/3] ACPICA: Fix access width for reset vector Matthew Garrett
2010-12-09 22:41 ` Rafael J. Wysocki
2010-12-09 23:12 ` H. Peter Anvin
2010-12-09 23:26 ` Matthew Garrett
2010-12-09 21:46 ` [PATCH 3/3] ACPI: Bug compatibility for Windows on the ACPI reboot vector Matthew Garrett
2010-12-09 22:36 ` H. Peter Anvin
2010-12-09 22:41 ` Rafael J. Wysocki
2010-12-09 22:25 ` [PATCH 1/3] X86: Revamp reboot behaviour to match Windows more closely H. Peter Anvin
2010-12-09 22:32 ` Matthew Garrett
2010-12-09 22:32 ` H. Peter Anvin
2010-12-09 22:38 ` Matthew Garrett [this message]
2010-12-09 22:40 ` H. Peter Anvin
2010-12-09 22:51 ` Matthew Garrett
2010-12-09 22:53 ` H. Peter Anvin
2010-12-09 22:58 ` Matthew Garrett
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=20101209223847.GA24452@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.