From: "Darrick J. Wong" <djwong@us.ibm.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] ipmisensors to use or not to use?
Date: Mon, 17 Nov 2008 22:33:24 +0000 [thread overview]
Message-ID: <20081117223324.GD8800@plum> (raw)
In-Reply-To: <4918C638.7010202@anduras.de>
On Mon, Nov 17, 2008 at 01:56:32PM -0800, Darrick J. Wong wrote:
> On Mon, Nov 17, 2008 at 06:05:30PM +0100, Sven Anders wrote:
> >
> > Hmm?!
> > Does nobody know or is nobody willing to answer?
> >
> > I'm thinking of updating the patch for newer kernel, but
> > as my time is limited, I would only do this, if it's the
> > right way and it has a chance to be integrated in the
> > kernel.
>
> As I recall, the driver needs to be ported to 2.6.28-rc. Both it and
> ibmpex try to call hwmon_device_register on the bmc device, which causes
> problems if someone tries to load both. I think there was a
> general unease with putting it in without some more code review. The
> author doesn't seem to be pushing for its inclusion. If nothing else, I
> did a quick port to 2.6.28-rc5 and it miscategorizes a power meter as a
> current sensor and the fan RPM sensors totally don't work. I might be
> able to clean it up a bit and then maybe we can push it into the
> scary-upcoming-drivers tree?
Blechk. Also crashes on rmmod, and it seems that the only thing that
works are the voltage sensors. Lots of strange looking code to convert
sensor readings too.
--D
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2008-11-17 22:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 23:39 [lm-sensors] ipmisensors to use or not to use? Sven Anders
2008-11-17 17:05 ` Sven Anders
2008-11-17 21:56 ` Darrick J. Wong
2008-11-17 22:33 ` Darrick J. Wong [this message]
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=20081117223324.GD8800@plum \
--to=djwong@us.ibm.com \
--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.