From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Gandalf Kristensen <gandkri@yahoo.no>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Lin, Ming M" <ming.m.lin@intel.com>
Subject: Re: Buggy BIOS on the HP TX2500-series
Date: Thu, 9 Oct 2008 02:11:50 +0100 [thread overview]
Message-ID: <20081009011150.GA7496@srcf.ucam.org> (raw)
In-Reply-To: <1223513955.2735.28.camel@rzhang-dt>
On Thu, Oct 09, 2008 at 08:59:15AM +0800, Zhang Rui wrote:
> On Wed, 2008-10-08 at 12:26 -0700, Matthew Garrett wrote:
> > A patch went into the kernel earlier this year to ignore critical trip
> > points that were below 0.
> well, I think this patch is wrong.
> a critical trip point below 0 Celsius doesn't mean it's invalid.
I think it's pretty clear that a critical trip point below 0 celsius
means that the critical trip point is invalid, though I agree that
ignoring the entire thermal zone as a result is somewhat unfortunate.
> windows can work well on this laptop.
> please look at:
> http://bugzilla.kernel.org/show_bug.cgi?id=10686#c13
> IMO, we need to fix the ACPICA code first of all.
>
> Ming, what do you think of the patch in comment #15 and #16?
We could quibble over the technical correctness of this approach, but it
seems to behave in exactly the same way - ie, Linux will ignore the
thermal zone? The existing code seems fine, other than the fact that a
bad _CRT will result everything failing. I think we'd be better off just
losing the return -ENODEV there and try to use as much of the thermal
information as we can.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-10-09 1:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 17:39 Buggy BIOS on the HP TX2500-series Gandalf Kristensen
2008-10-08 19:26 ` Matthew Garrett
2008-10-08 20:09 ` Buggy BIOS on the HP tx2500-series Gandalf Kristensen
2008-10-09 0:59 ` Buggy BIOS on the HP TX2500-series Zhang Rui
2008-10-09 1:10 ` Len Brown
2008-10-09 1:11 ` Matthew Garrett [this message]
2008-10-09 2:04 ` Len Brown
2008-10-09 4:16 ` Moore, Robert
2008-10-09 6:39 ` Zhang Rui
2008-10-09 6:43 ` Lin Ming
2008-10-09 6:36 ` Zhang Rui
2008-10-09 6:45 ` Zhang Rui
2008-10-09 14:18 ` Moore, Robert
2008-10-09 9:52 ` Thomas Renninger
2008-10-09 1:32 ` Lin Ming
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=20081009011150.GA7496@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=gandkri@yahoo.no \
--cc=linux-acpi@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=rjw@sisk.pl \
--cc=rui.zhang@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.