mirror of
https://github.com/lm-sensors/lm-sensors.git
synced 2026-10-31 13:10:30 +00:00
updates
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@1648 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
1 parent
ad2705bd37
commit
239017d880
5 files changed
+56
-6
No files matched your search
@@ -42,6 +42,7 @@ ask CVS about it:
|
||||
Module i2c-amd8111: New (SMBus 2.0)
|
||||
Module i2c-ipmb: New
|
||||
Module i2c-ipmi: New
|
||||
Module i2c-keywest: Sync with kernel 2.4.20
|
||||
Module i2c-sis630: Add support for SiS730
|
||||
Module i2c-sis645: Improve support for SiS645/961;
|
||||
add support for SiS645DX/961 and SiS735
|
||||
@@ -51,7 +52,7 @@ ask CVS about it:
|
||||
Module vt8231: Fix inx limits and alarms; fix in0
|
||||
Module w83781d: Fix in0/in1 initialization
|
||||
Module smartbatt: New
|
||||
Modules (several): Remove #ifndefs, require i2c-2.7.0
|
||||
Modules (several): Remove #ifndefs, require i2c-2.7.0; HZ fixes
|
||||
Program decode-dimms.pl: Code cleanup; valid HTML; better HTML output;
|
||||
stop decoding on checksum error
|
||||
Program dmidecode: Fix read bug; upgrade to version 1.8
|
||||
@@ -66,7 +67,7 @@ ask CVS about it:
|
||||
fix w83781d temp3 alarm; fix gl518sm rev 0x00 recognition;
|
||||
initial support for Sony Vaio eeprom
|
||||
Program sensors-detect: Add support for MC1066, smart battery, 8235,
|
||||
IPMI, AMD8111;
|
||||
IPMI, AMD8111; add help if no sensors found;
|
||||
add ACPI method for IBM system detection;
|
||||
work with old Perl versions again;
|
||||
initial support for Sony Vaio eeprom
|
||||
|
||||
+8
-2
@@ -131,8 +131,8 @@ sis5595
|
||||
smartbatt
|
||||
smartbatt 1 1 - - yes no
|
||||
|
||||
smsc74m1
|
||||
smsc74m1 - - 2 2 no yes (LPC)
|
||||
smsc47m1
|
||||
smsc47m1 - - 2 2 no yes (LPC)
|
||||
|
||||
thmc50
|
||||
adm1022 3 2 - 1 dac yes no
|
||||
@@ -145,6 +145,9 @@ via686a
|
||||
vt1211
|
||||
vt1211 2-7 2-7 2 2 no yes (LPC)
|
||||
|
||||
vt8231
|
||||
vt8231 2-7 2-7 2 2 no yes
|
||||
|
||||
w83781d
|
||||
as99127f 3 7 3 2 pwm? yes no
|
||||
w83781d 3 7 3 - yes yes
|
||||
@@ -162,6 +165,9 @@ SUPPORTED NON-SENSOR CHIPS
|
||||
Driver Chips
|
||||
------ -----
|
||||
|
||||
bmcsensors
|
||||
An interface to an IPMI BMC (Baseboard management controller)
|
||||
|
||||
bt869
|
||||
bt869 video modulator chip
|
||||
|
||||
|
||||
@@ -47,11 +47,15 @@ You must configure the following features in your kernel
|
||||
IPMI KCS handler
|
||||
The IPMI device interface and IPMI watchdog handler are not required.
|
||||
|
||||
You must modprobe i2c-ipmi separately, it will not
|
||||
load automatically when you modprobe bmcsensors.
|
||||
|
||||
If the KCS handler (ipmi_kcs_drv) is configured as a module,
|
||||
you must modprobe it separately, it will not load automatically
|
||||
you must also modprobe it separately, it will not load automatically
|
||||
when you modprobe i2c-ipmi or ipmi_msghandler (unless you set up
|
||||
/etc/modules.conf to load ipmi_kcs_drv when ipmi_msghandler is loaded).
|
||||
|
||||
|
||||
/proc entries
|
||||
-------------
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
These are the steps you should follow to write a new driver and
|
||||
submit it to us so that it will be applied cleanly to our package.
|
||||
See at the bottom for adding new chip support to an existing driver.
|
||||
|
||||
Don't be intimidated by the list, it's just here so we don't
|
||||
forget anything.
|
||||
@@ -37,6 +38,7 @@ Steps which apply to only one type of driver are noted.
|
||||
Be sure and use 8 column tabs.
|
||||
Also, please do not use // comments.
|
||||
Also, please do not go past column 80.
|
||||
Also, please use C99 struct initializers {.foo = blat}
|
||||
Please do this _before_ you check in your driver.
|
||||
|
||||
* Add sysctl definitions to kernel/include/sensors.h (for chip drivers only).
|
||||
@@ -140,3 +142,33 @@ Checklist for mkpatch support, after the driver is tested and stable:
|
||||
|
||||
* Move .o reference in kernel/[chips,busses]/Module.mk
|
||||
from first to second section.
|
||||
|
||||
|
||||
---------------------------------------------------------------------
|
||||
Checklist for _adding_ support for a chip to an _existing_ driver:
|
||||
|
||||
* Make the changes to the driver itself.
|
||||
|
||||
* Add detection information to prog/detect/sensors-detect.
|
||||
|
||||
* Add a strncmp() call for the new prefix in prog/sensors/main.c
|
||||
(chip drivers only).
|
||||
|
||||
* Add entries for the new prefix to etc/sensors.conf.eg (chip drivers only).
|
||||
|
||||
* Update config help in mkpatch/mkpatch.pl.
|
||||
|
||||
* Update config entry in mkpatch/Config.in (chip drivers only)
|
||||
|
||||
* Update config entry in mkpatch/mkpatch.pl (bus drivers only)
|
||||
|
||||
* Update doc/[chips,busses]/xxx file
|
||||
|
||||
* Update doc/chips/SUMMARY file (chip drivers only)
|
||||
|
||||
* Update list in README
|
||||
|
||||
* Submit the changes as a patch or check them in
|
||||
|
||||
* Update entry on 'new drivers' page
|
||||
|
||||
+8
-1
@@ -34,12 +34,19 @@ There is no facility in the lm_sensors package for drivers
|
||||
to output general strings via /proc. This facility may be added
|
||||
in the future.
|
||||
|
||||
Alarms are direct indications read from the chips. The drivers do NOT make
|
||||
comparisons of readings to thresholds. This allows violations
|
||||
between readings to be caught and alarmed. The exact definition of
|
||||
an alarm (for example, whether a threshold must be met or must be
|
||||
exceeded to cause an alarm) is chip-dependent.
|
||||
|
||||
Guidelines for new entries:
|
||||
- If there are multiple values, some r/w and some r/o,
|
||||
put the r/w ones first.
|
||||
- Additional non-standard values should be after the standard values.
|
||||
|
||||
|
||||
|
||||
-------------------------------------------------------------------------
|
||||
|
||||
/proc entries are as follows:
|
||||
@@ -66,7 +73,7 @@ beep 2 Beep/interrupt enable and bitmask.
|
||||
same format as 'alarms' with same bit locations.
|
||||
|
||||
curr[1-n] 3 Current max, min or hysteresis, and input value.
|
||||
Floating point values XXX.X or XXX.XX in Amps.
|
||||
Floating point values XX.X or XX.XX in Amps.
|
||||
The second value is preferably a hysteresis value,
|
||||
reported as a absolute current, NOT a delta from
|
||||
the max value.
|
||||
|
||||
Reference in new issue
Block a user