From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: "Koornstra, Reinoud" <koornstra@hp.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>,
"Lin, Ming M" <ming.m.lin@intel.com>,
"Zhao, Yakui" <yakui.zhao@intel.com>
Subject: Re: 2.6.28-rc7 acpi error messages
Date: Fri, 5 Dec 2008 17:21:44 +0000 [thread overview]
Message-ID: <20081205172144.GA27396@srcf.ucam.org> (raw)
In-Reply-To: <4911F71203A09E4D9981D27F9D8308580DD53D76@orsmsx503.amr.corp.intel.com>
On Fri, Dec 05, 2008 at 08:58:39AM -0800, Moore, Robert wrote:
> >> 1) Use the RSDT instead of the XSDT and automatically get the "correct"
> >FADT with no 64-bit register definitions.
> >>
> >> 2) Use the XSDT as is done today, but use the 32-bit values instead of
> >the 64-bit values in the extended FADT.
>
>
> What we really want to know is what does windows do, (1), or (2).
So far I haven't managed to find any machines that have differing values
in the version 1 FADT and the 32-bit values of the version 2 one, so
it's difficult to know. Best bet would probably be a qemu setup that
feeds different values for this - I think some people in Intel had
something like this for some previous testing?
next prev parent reply other threads:[~2008-12-05 17:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 21:22 2.6.28-rc7 acpi error messages Koornstra, Reinoud
2008-12-03 22:43 ` Moore, Robert
2008-12-03 23:03 ` Matthew Garrett
2008-12-03 23:12 ` Moore, Robert
2008-12-03 23:35 ` Matthew Garrett
2008-12-04 1:22 ` Koornstra, Reinoud
2008-12-04 2:08 ` Zhao Yakui
2008-12-04 15:50 ` Moore, Robert
2008-12-04 19:03 ` Koornstra, Reinoud
2008-12-04 20:31 ` Moore, Robert
2008-12-04 21:08 ` Matthew Garrett
2008-12-04 22:49 ` Moore, Robert
2008-12-04 23:02 ` Matthew Garrett
2008-12-05 16:32 ` Moore, Robert
2008-12-05 16:37 ` Matthew Garrett
2008-12-05 16:58 ` Moore, Robert
2008-12-05 17:01 ` Skywing
2008-12-05 17:21 ` Matthew Garrett [this message]
2008-12-05 17:42 ` Moore, Robert
2008-12-05 17:48 ` Matthew Garrett
2008-12-05 17:57 ` Koornstra, Reinoud
2008-12-05 19:55 ` Koornstra, Reinoud
2008-12-03 23:06 ` Koornstra, Reinoud
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=20081205172144.GA27396@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=koornstra@hp.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=robert.moore@intel.com \
--cc=yakui.zhao@intel.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 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.