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>
Subject: Re: 2.6.28-rc7 acpi error messages
Date: Wed, 3 Dec 2008 23:35:57 +0000 [thread overview]
Message-ID: <20081203233557.GA27180@srcf.ucam.org> (raw)
In-Reply-To: <4911F71203A09E4D9981D27F9D8308580DD52F0F@orsmsx503.amr.corp.intel.com>
On Wed, Dec 03, 2008 at 03:12:55PM -0800, Moore, Robert wrote:
> Not even the 32-bit values seem fully correct, however. For example:
>
> [05Ch 092 1] GPE0 Block Length : 10
>
>
> [0DCh 220 12] GPE0 Block : <Generic Address Structure>
> [0DCh 220 1] Space ID : 01 (SystemIO)
> [0DDh 221 1] Bit Width : 20
> [0DEh 222 1] Bit Offset : 00
> [0DFh 223 1] Access Width : 00
> [0E0h 224 8] Address : 000000000001F028
>
>
> For the first block length, I seriously doubt that the machine has (0x10 * 8) = 128 GPEs. The bit width of 0x20 (32 GPEs) sounds more reasonable.
Hmm, indeed - Intel hardware only decodes 32-bits for the GPE block. Do
we have the version 1 FADT from the machine as well? If that's correct
it suggests that Windows gets all of this information from there rather
than using the version 2 table at all, while if it isn't perhaps we need
to take the width from the 64-bit values. Sigh. What a mess.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-12-03 23:36 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 [this message]
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
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=20081203233557.GA27180@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 \
/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.