From: Robert Delahunt <twinreverb@puresimplicity.net>
To: linux-i2c@vger.kernel.org
Cc: linux-acpi@vger.kernel.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 20:17:42 +0900 [thread overview]
Message-ID: <200811182017.43109.twinreverb@puresimplicity.net> (raw)
In-Reply-To: <049.52c5d9ff015802332972920378e356e9@lm-sensors.org>
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?
As for this laptop, thermal regulating is actually controlled in the hardware:
neither ACPI nor sensors/i2c is needed to regulate temperature in the OS
level. I just find it odd that i2c/lm_sensors claims to support this chipset
yet the answer I get is that the kernel ACPI "hides" them.
I'll bring this up to the kernel ACPI developers, but I would like to see this
issue resolved. Again, I am willing to test out whatever code necessary to
help this process.
On Tuesday 18 November 2008 06:20:48 pm lm-sensors wrote:
> #2361: i2c and lm_sensors do not work on Slackware 12.1 with kernel
> 2.6.27.6
> ----------------------+----------------------------------------------------
>- Reporter: ticket | Owner: somebody
> Type: defect | Status: closed
> Priority: major | Milestone:
> Component: sensors | Version: 3.0.3
> Resolution: fixed | Keywords:
> ----------------------+----------------------------------------------------
>- Changes (by khali):
>
> * cc: twinreverb@puresimplicity.net. (added)
> * status: new => closed
> * resolution: => fixed
> * milestone: 3.0.4 =>
>
> Comment:
>
> I don't see anything wrong here. Most laptops do not have (exposed)
> hardware monitoring chips. Thermal regulation is handled by ACPI.
--
Very respectfully,
Robert Delahunt
-------------------------------------------------------------------
Ezekiel 11:19 New King James Version
Then I will give them one heart, and I will put a new spirit within
them, and take the stony heart out of their flesh, and give them a
heart of flesh....
next parent reply other threads:[~2008-11-18 11:17 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 ` Robert Delahunt [this message]
[not found] ` <200811182017.43109.twinreverb-v3ax9e/3W6w7GzjB842lBqxOck334EZe@public.gmane.org>
2008-11-18 11:42 ` [lm-sensors] #2361: i2c and lm_sensors do not work on Slackware 12.1 with kernel 2.6.27.6 Matthew Garrett
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=200811182017.43109.twinreverb@puresimplicity.net \
--to=twinreverb@puresimplicity.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@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