Porting OpenBSD's sysctl hw.sensors framework to FreeBSD
M. Warner Losh
imp at bsdimp.com
Wed Jul 11 02:59:44 UTC 2007
In message: <200707101833.l6AIX0xl049962 at ambrisko.com>
Doug Ambrisko <ambrisko at ambrisko.com> writes:
: John-Mark Gurney writes:
: | Constantine A. Murenin wrote this message on Sat, Jul 07, 2007 at 21:43 -0400:
: | > Hardware sensors tree is going to be pretty deep down. Under sysctl(8)
: | > the variable names will look like this:
: | >
: | > hw.sensors.lm0.temp0
: | >
: | > whereas in reality, the tree has five levels:
: | >
: | > hw.sensors.lm0.temp.0
: |
: | I'm curious, why do we want/need these in the kernel as opposed to a
: | userland library/utility to provide this info?
:
: I agree. There are so many different flavours of HW monitoring chips
: and several tools that can read them live in ports. Lots of them are
: slightly different, intefaces can be i2c or direct I/O. We are already
: somewhat battling with the various ways IPMI controllers can be attached
: to the system. Now in the case of IPMI there is a good win in providing
: a device driver interface for the HW and user land tools to get info.
: out of them. I don't see a win with this in the various HW monitoring
: chips.
My big concern is the 'automatic' probing. It doesn't mix well with
i2c eeprom chips :-(
Warner
More information about the freebsd-arch
mailing list