From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org,
Jean Delvare <khali@linux-fr.org>,
"Thomas, Sujith" <sujith.thomas@intel.com>
Subject: Re: The new thermal management sysfs class, and hwmon
Date: Thu, 7 Feb 2008 01:41:33 -0500 [thread overview]
Message-ID: <200802070141.33362.lenb@kernel.org> (raw)
In-Reply-To: <20080203175006.GB9159@khazad-dum.debian.net>
> Agreed. However, *duplicating* what is already in hwmon elsewhere is not
> fun. Please reconsider.
I started off with the same position as you, Henrique,
but Rui and Sujith don't see it that way.
Of course this is software, we can always change it --
particularly since there will be a very small list
of users for the new I/F, and we happen to know them:-)
> I'd like to see passive cooling (heck, the entire
> ACPI v3.0 thermal model, if needed) added to hwmon, that will enhance hwmon
> to be even more generic, and we all benefit from that.
The ACPI 3.0 thermal model requires quite a bit of sophistication from
the system designer and BIOS writer.
Based on the quality of system designs and BIOS code we see
in the industry, I think it is way over the head of 99% of the industry.
That said, if a system does come out that supports the ACPI 3.0 Thermal Model
and they want to ship Linux on it, we can look into it then.
cheers,
-Len
WARNING: multiple messages have this Message-ID (diff)
From: Len Brown <lenb@kernel.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: "Mark M. Hoffman" <mhoffman@lightlink.com>,
Zhang Rui <rui.zhang@intel.com>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org,
Jean Delvare <khali@linux-fr.org>,
"Thomas, Sujith" <sujith.thomas@intel.com>
Subject: Re: [lm-sensors] The new thermal management sysfs class, and hwmon
Date: Thu, 07 Feb 2008 06:41:33 +0000 [thread overview]
Message-ID: <200802070141.33362.lenb@kernel.org> (raw)
In-Reply-To: <20080203175006.GB9159@khazad-dum.debian.net>
> Agreed. However, *duplicating* what is already in hwmon elsewhere is not
> fun. Please reconsider.
I started off with the same position as you, Henrique,
but Rui and Sujith don't see it that way.
Of course this is software, we can always change it --
particularly since there will be a very small list
of users for the new I/F, and we happen to know them:-)
> I'd like to see passive cooling (heck, the entire
> ACPI v3.0 thermal model, if needed) added to hwmon, that will enhance hwmon
> to be even more generic, and we all benefit from that.
The ACPI 3.0 thermal model requires quite a bit of sophistication from
the system designer and BIOS writer.
Based on the quality of system designs and BIOS code we see
in the industry, I think it is way over the head of 99% of the industry.
That said, if a system does come out that supports the ACPI 3.0 Thermal Model
and they want to ship Linux on it, we can look into it then.
cheers,
-Len
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-02-07 6:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 2:26 The new thermal management sysfs class, and hwmon Henrique de Moraes Holschuh
2008-02-03 2:26 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-03 9:31 ` Zhang Rui
2008-02-03 9:31 ` [lm-sensors] " Zhang Rui
2008-02-03 16:44 ` Mark M. Hoffman
2008-02-03 16:44 ` [lm-sensors] " Mark M. Hoffman
2008-02-03 17:50 ` Henrique de Moraes Holschuh
2008-02-03 17:50 ` [lm-sensors] " Henrique de Moraes Holschuh
2008-02-05 10:14 ` Thomas, Sujith
2008-02-05 10:26 ` [lm-sensors] " Thomas, Sujith
2008-02-05 13:57 ` Mark M. Hoffman
2008-02-05 13:57 ` [lm-sensors] " Mark M. Hoffman
2008-02-05 14:55 ` Henrique de Moraes Holschuh
2008-02-05 14:55 ` Henrique de Moraes Holschuh
2008-02-07 7:01 ` Len Brown
2008-02-07 7:01 ` Len Brown
2008-02-07 12:30 ` Henrique de Moraes Holschuh
2008-02-07 12:30 ` Henrique de Moraes Holschuh
2008-02-06 5:23 ` Thomas, Sujith
2008-02-06 5:35 ` [lm-sensors] " Thomas, Sujith
2008-02-13 15:10 ` Thomas Renninger
2008-02-13 15:10 ` [lm-sensors] " Thomas Renninger
2008-02-14 14:08 ` Matthew Garrett
2008-02-14 14:08 ` [lm-sensors] " Matthew Garrett
2008-02-15 11:04 ` Thomas, Sujith
2008-02-15 11:16 ` [lm-sensors] " Thomas, Sujith
2008-02-15 11:56 ` Matthew Garrett
2008-02-15 11:56 ` [lm-sensors] " Matthew Garrett
2008-02-15 12:19 ` Henrique de Moraes Holschuh
2008-02-15 12:19 ` Henrique de Moraes Holschuh
2008-02-22 5:47 ` zhangrui
2008-02-22 5:47 ` [lm-sensors] " zhangrui
2008-02-22 8:00 ` Hans de Goede
2008-02-22 8:00 ` Hans de Goede
2008-02-22 8:33 ` Zhang, Rui
2008-02-22 8:33 ` Zhang, Rui
2008-02-22 10:54 ` Hans de Goede
2008-02-22 10:54 ` Hans de Goede
2008-02-23 7:43 ` Len Brown
2008-02-23 7:43 ` Len Brown
2008-02-23 8:29 ` Jean Delvare
2008-02-23 8:29 ` [lm-sensors] " Jean Delvare
2008-02-24 22:52 ` Zhang, Rui
2008-02-24 22:52 ` [lm-sensors] " Zhang, Rui
2008-02-25 8:53 ` Hans de Goede
2008-02-25 8:53 ` [lm-sensors] " Hans de Goede
2008-02-23 20:39 ` Henrique de Moraes Holschuh
2008-02-23 20:39 ` Henrique de Moraes Holschuh
2008-02-07 6:41 ` Len Brown [this message]
2008-02-07 6:41 ` Len Brown
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=200802070141.33362.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=hmh@hmh.eng.br \
--cc=khali@linux-fr.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=rui.zhang@intel.com \
--cc=sujith.thomas@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.