From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] ipmisensors module ported to 2.6.29
Date: Thu, 19 Nov 2009 09:56:29 +0000 [thread overview]
Message-ID: <4B05164D.9070506@hhs.nl> (raw)
In-Reply-To: <1258584180.8521.102.camel@pharper_desktop.arrs.arrisi.com>
Hi,
On 11/18/2009 11:43 PM, Paul Harper wrote:
> I have ported the ipmisensors module to kernel version 2.6.29 and
> corrected the issues with fatal errors on loading and swizzling of
> device data. On my IBM development platform (3650) the module now works
> as expected and data from ipmitool and lm-sensors is in sync.
>
> I then did a test on a SuperMicro chassis and the module could not
> connect to the bmc. ipmitool works as expected on the SuperMicro. In
> examination of the ipmitool code, it appears that they have moved to
> IPMB comms rather than a direct connect to the BMC.
>
> Before I start changing ipmisensors to use IPMB comms, is there another
> preferred module to use when exposing sensors to lm-sensors and the
> vendor provides impi support?
>
This is just my 2 cents, so before you actually act on this, it would be
good to get a second opinion, say Jean Delvare's .
Given that there already are various userspace options to reading ipmi
sensors, which I assume work as non root (iow no direct io banging). An
alternative to using a kernel driver might be the extend libsensors
to be able to read sensor info from other sources then the hwmon
sysfs interface.
what I envision is:
1) abstraction of sensor source enumeration and reading in libsensors
2) a plugin architecture to add support for different sensor sources
3) Various plugins for example:
hwmon sysfs (of course)
something to read harddisk temps using smart
code to read ipmi info
I think this would be really nice to have as currently many applications
have support for both libsensors and have separate code for things like
harddisks temps, etc. libsensors seems like a logical place to consolidate
this.
I must warn though, that this will require some surgery to libsensors, it was
never designed to do this.
If you are willing to spend effort on this, I would be happy to help were I
can!
Regards,
Hans
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-11-19 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 22:43 [lm-sensors] ipmisensors module ported to 2.6.29 Paul Harper
2009-11-19 9:56 ` Hans de Goede [this message]
2009-11-19 10:46 ` Jean Delvare
2009-11-19 11:22 ` Luca Tettamanti
2009-11-19 12:09 ` Jean Delvare
2009-11-19 12:35 ` Luca Tettamanti
2009-11-19 12:51 ` Jean Delvare
2009-11-19 13:00 ` Philip Pokorny
2009-11-19 18:46 ` Paul Harper
2009-12-02 15:32 ` Luca Tettamanti
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=4B05164D.9070506@hhs.nl \
--to=j.w.r.degoede@hhs.nl \
--cc=lm-sensors@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 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.