From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: Robert Delahunt
<twinreverb-v3ax9e/3W6w7GzjB842lBqxOck334EZe@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [lm-sensors] #2361: i2c and lm_sensors do not work on Slackware 12.1 with kernel 2.6.27.6
Date: Tue, 18 Nov 2008 11:42:21 +0000 [thread overview]
Message-ID: <20081118114221.GA28706@srcf.ucam.org> (raw)
In-Reply-To: <200811182017.43109.twinreverb-v3ax9e/3W6w7GzjB842lBqxOck334EZe@public.gmane.org>
On Tue, Nov 18, 2008 at 08:17:42PM +0900, Robert Delahunt wrote:
> How is it fixed? ACPI and sensors should be able to live together. If I
> can't have one without the other, in my opinion, this is a blind spot for
> both projects. Has anyone brought this up to the kernel ACPI developers to
> see if they can "unhide" or "expose" the hardware monitoring?
Hitting thermal regulation hardware directly can cause problems if
you're also using ACPI, since there's no way of implementing locking
between the firmware and the operating system in this case. Since most
thermal monitoring hardware is accessed using indexed registers, having
two pieces of code trying to access the hardware simultaneously will
give bogus values and potentially result in hardware damage. Many
laptops therefore hide the smbus from the operating system. While it's
possible to unhide them, it's not a good idea.
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
next prev parent reply other threads:[~2008-11-18 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <040.878a61a6a191c2ece367aefb3b3bc643@lm-sensors.org>
[not found] ` <049.52c5d9ff015802332972920378e356e9@lm-sensors.org>
2008-11-18 11:17 ` [lm-sensors] #2361: i2c and lm_sensors do not work on Slackware 12.1 with kernel 2.6.27.6 Robert Delahunt
[not found] ` <200811182017.43109.twinreverb-v3ax9e/3W6w7GzjB842lBqxOck334EZe@public.gmane.org>
2008-11-18 11:42 ` Matthew Garrett [this message]
2008-11-18 16:02 ` Jean Delvare
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=20081118114221.GA28706@srcf.ucam.org \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=twinreverb-v3ax9e/3W6w7GzjB842lBqxOck334EZe@public.gmane.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