public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Koornstra, Reinoud" <koornstra@hp.com>
Cc: Len Brown <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: rc8 didn't include patch (was Re: 2.6.28-rc7 acpi error messages)
Date: Fri, 12 Dec 2008 21:02:10 +0000	[thread overview]
Message-ID: <20081212210210.GA28575@srcf.ucam.org> (raw)
In-Reply-To: <E92FAF79A8BBC642A36EEE3AA7F152D82A17319841@GVW1089EXB.americas.hpqcorp.net>

On Fri, Dec 12, 2008 at 07:22:47PM +0000, Koornstra, Reinoud wrote:
> What can I do to help out in this?
> I could install windows on this machine as well, but I guess you'd be more interested in how this is supported under windows and just seeing that it's supported well under windows doesn't give the info that's needed.
> Since it's HP hardware, HP must have provided detailed specs to MS to be able to do this well, that is ......
> IF it's being supported well.

We need to know the precise behaviour of Windows in this case. It's 
clearly using the 32-bit values by default, but we are currently unsure 
whether it's taking them from the FADT pointed to by the RSDT or the 
XSDT. My patch assumes the latter. I suspect that this is better than 
Linux's current behaviour and so I think we should push it anyway 
(though perhaps not until the 2.6.29 timeframe), but confirmation as to 
its correctness would be helpful.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

      reply	other threads:[~2008-12-12 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12  1:15 rc8 didn't include patch (was Re: 2.6.28-rc7 acpi error messages) Koornstra, Reinoud
2008-12-12  6:39 ` Len Brown
2008-12-12 19:22   ` Koornstra, Reinoud
2008-12-12 21:02     ` Matthew Garrett [this message]

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=20081212210210.GA28575@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=koornstra@hp.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox