Somehow, this commit seems to have failed before. Nothing major: added
an entry in the manpage, fixed a spelling error in main.c and added
a CHANGES entry.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@848 7894878c-1315-0410-8ee3-d5d059ff63e0
4 banks per memory chip. Add banks entry to libsensors and
use # of banks in calculation.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@839 7894878c-1315-0410-8ee3-d5d059ff63e0
can flag chassis intrusion detection to be ignored, etc. Updated
CHANGES to reflect this and updates to sensord.
-- merlin
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@837 7894878c-1315-0410-8ee3-d5d059ff63e0
ALERT so you can pick them up in syslog.conf and fire them to
the console, etc. Added support for scanning only for alarms
in addition to scanning regular values, etc. Updated the man
file to reflect the new options, etc. Operation as "sensors"
command is undocumented.
-- merlin
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@835 7894878c-1315-0410-8ee3-d5d059ff63e0
. added support for via686a and other new chips
. added support for alarms and beeps
. updated to log through syslog instead of a custom logfile
. updated so when run as "sensors" (ln -s sensord sensors) it
mimics the existing sensors command except for formatting
. modularized a bit
Yet to do:
. complete support for alarm checking without sensor logging
. signal alarms through syslog level ALERT
. add final support for multivalued alarms
. check up on some questions about existing sensors command
. update manual page inc. notes on syslog usage
. test more fully
-- merlin
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@828 7894878c-1315-0410-8ee3-d5d059ff63e0
* W83783S now correctly assumes only one LM75-like chip address
* No more runtime-errors if an unknown adapter was found.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@825 7894878c-1315-0410-8ee3-d5d059ff63e0
It may be very close or very far from working. At this point, scanning a
bus gives a bunch of errors, but seems to do different things around
addresses which could very well have devices, so it seems promising.
Hopefully, it's just something silly I'm missing like an 'ack'.
Pretty good for not having *any* technical documentation on the driver,
except a partially written (and maybe not even working) example code
from Apple.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@813 7894878c-1315-0410-8ee3-d5d059ff63e0
what there is now. What's left is to use the registers of the keywest
to communicate with devices on the bus. (I.e., flesh out the 'access'
routine.)
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@812 7894878c-1315-0410-8ee3-d5d059ff63e0
commit, the module can detect and read the registers from compatible
Keywest buss(es). (Note: there may be more than one bus, as I seem to have.)
Probing is done via Apple's 'New World' Open-Firmware rather than PCI. In
this way, this driver should work with any I2C bus (when it is completed)
which is Keywest 'compatible'. The down side is that this module won't
work on anything but a newer Apple PPC.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@811 7894878c-1315-0410-8ee3-d5d059ff63e0
Frodo Looijaard