mirror of
https://github.com/lm-sensors/lm-sensors.git
synced 2026-11-21 19:51:45 +00:00
Merge from trunk (4303:4355) out to 3.0.0 branch.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4357 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
1 parent
2bb6b1859a
commit
c5ffa7b635
50 files changed
+1024
-888
No files matched your search
@@ -9,7 +9,7 @@ Supported adapters:
|
||||
Datasheet: Publicly available at the Intel website
|
||||
* ServerWorks OSB4, CSB5, CSB6 and HT-1000 southbridges
|
||||
Datasheet: Only available via NDA from ServerWorks
|
||||
* ATI IXP southbridges IXP200, IXP300, IXP400
|
||||
* ATI IXP200, IXP300, IXP400 and SB600 southbridges
|
||||
Datasheet: Not publicly available
|
||||
* Standard Microsystems (SMSC) SLC90E66 (Victory66) southbridge
|
||||
Datasheet: Publicly available at the SMSC website http://www.smsc.com
|
||||
|
||||
@@ -10,7 +10,10 @@ Supported adapters:
|
||||
Datasheet: Sometimes available at the VIA website
|
||||
|
||||
* VIA Technologies, Inc. VT8231, VT8233, VT8233A, VT8235, VT8237R/A, VT8251
|
||||
Datasheet: available on request from Via
|
||||
Datasheet: available on request and under NDA from VIA
|
||||
|
||||
* VIA Technologies, Inc. CX700
|
||||
Datasheet: available on request and under NDA from VIA
|
||||
|
||||
Authors:
|
||||
Kyösti Mälkki <kmalkki@cc.hut.fi>
|
||||
@@ -45,6 +48,7 @@ Your /proc/pci or lspci -n listing must show one of these :
|
||||
device 1106:3227 (VT8237R)
|
||||
device 1106:3337 (VT8237A)
|
||||
device 1106:3287 (VT8251)
|
||||
device 1106:8324 (CX700)
|
||||
|
||||
If none of these show up, you should look in the BIOS for settings like
|
||||
enable ACPI / SMBus or even USB.
|
||||
@@ -52,3 +56,6 @@ enable ACPI / SMBus or even USB.
|
||||
Except for the oldest chips (VT82C596A/B, VT82C686A and most probably
|
||||
VT8231), this driver supports I2C block transactions. Such transactions
|
||||
are mainly useful to read from and write to EEPROMs.
|
||||
|
||||
The CX700 additionally appears to support SMBus PEC, although this driver
|
||||
doesn't implement it.
|
||||
@@ -220,6 +220,8 @@ smsc47m1
|
||||
smsc47m15x - - 2 2 no yes (LPC)
|
||||
smsc47m192 - - 2 2 no yes (LPC)
|
||||
smsc47m997 - - 2 2 no yes (LPC)
|
||||
(reported as a "smsc47m2")
|
||||
smsc47m292 - - 3 3 no yes (LPC)
|
||||
|
||||
thmc50
|
||||
adm1022 3 2 - 1 dac yes no
|
||||
|
||||
+1
-1
@@ -176,7 +176,7 @@ SMBus Read Byte, and PEC will work properly.
|
||||
Additionally, the ADM1032 doesn't support SMBus Send Byte with PEC.
|
||||
Instead, it will try to write the PEC value to the register (because the
|
||||
SMBus Send Byte transaction with PEC is similar to a Write Byte transaction
|
||||
without PEC), which is not what we want. Thus, PEC is explicitely disabled
|
||||
without PEC), which is not what we want. Thus, PEC is explicitly disabled
|
||||
on SMBus Send Byte transactions in the lm90 driver.
|
||||
|
||||
PEC on byte data transactions represents a significant increase in bandwidth
|
||||
|
||||
+8
-8
@@ -4,7 +4,7 @@ Sensors chip driver for MAXIM MAX6650 / MAX6651 fan controllers
|
||||
Chip notes
|
||||
----------
|
||||
|
||||
The MAX6551 is a fan controller. It has two distinct functions:
|
||||
The MAX6651 is a fan controller. It has two distinct functions:
|
||||
|
||||
1) Speed control, with feedback, for a single fan. The code can write
|
||||
to a register requesting that the fan run at a certain speed, and the
|
||||
@@ -14,7 +14,7 @@ The MAX6551 is a fan controller. It has two distinct functions:
|
||||
2) Speed measurement (tachometers) for up to four fans, including the
|
||||
controlled one.
|
||||
|
||||
The MAX6550 is similar but only has one measurement tachometer.
|
||||
The MAX6650 is similar but only has one measurement tachometer.
|
||||
|
||||
Both chips have a few general purpose i/o pins, some of which can be
|
||||
configured to have special functions. At the time of writing an overview
|
||||
@@ -22,7 +22,7 @@ of the chip, with links to the datasheet, can be seen at:
|
||||
|
||||
http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2296/ln/en
|
||||
|
||||
If that has moved searching for MAX6550 from Maxim's home page should
|
||||
If that has moved searching for MAX6650 from Maxim's home page should
|
||||
work.
|
||||
|
||||
Driver state
|
||||
@@ -79,9 +79,9 @@ Bugs
|
||||
configuration dynamically instead of assuming that some other code has
|
||||
done it.
|
||||
|
||||
o It does not differentiate between a MAX6550 and a MAX6551, as I can
|
||||
see no obvious way to do this. It has only been tested with a MAX6551
|
||||
so if anyone gets a board with a MAX6550 to test with maybe something
|
||||
o It does not differentiate between a MAX6650 and a MAX6651, as I can
|
||||
see no obvious way to do this. It has only been tested with a MAX6651
|
||||
so if anyone gets a board with a MAX6650 to test with maybe something
|
||||
will be revealed, such as the three missing tachometer registers
|
||||
returning all ones or something. (OK, so maybe I should have called
|
||||
this driver max6651, and ignored the max6650 totally...)
|
||||
@@ -96,13 +96,13 @@ The module will autodetect the presence of a max6650 or max6651 at any
|
||||
of the four possible I2C addresses for these devices. There is no ID
|
||||
register, but there are several registers with all zero bits at the
|
||||
high end. The driver checks that all of these are in fact zero before
|
||||
declaring the chip to be a MAX6550/1.
|
||||
declaring the chip to be a MAX6650/1.
|
||||
|
||||
sensors-detect
|
||||
--------------
|
||||
|
||||
Support for MAX6650/1 has been added to sensors-detect. It has been
|
||||
tested as correctly detecting a MAX6551 at I2C address 0x1B. Like the
|
||||
tested as correctly detecting a MAX6651 at I2C address 0x1B. Like the
|
||||
driver, it cannot yet distinguish a MAX6650 and MAX6651.
|
||||
|
||||
prog/sensors
|
||||
|
||||
+7
-3
@@ -16,6 +16,10 @@ Supported chips:
|
||||
http://www.smsc.com/main/datasheets/47m14x.pdf
|
||||
http://www.smsc.com/main/tools/discontinued/47m15x.pdf
|
||||
http://www.smsc.com/main/datasheets/47m192.pdf
|
||||
* SMSC LPC47M292
|
||||
Prefix: 'smsc47m2'
|
||||
Addresses scanned: none, address read from Super I/O config space
|
||||
Datasheet: Not public
|
||||
* SMSC LPC47M997
|
||||
Addresses scanned: none, address read from Super I/O config space
|
||||
Prefix: 'smsc47m1'
|
||||
@@ -41,9 +45,9 @@ Description
|
||||
The Standard Microsystems Corporation (SMSC) 47M1xx Super I/O chips
|
||||
contain monitoring and PWM control circuitry for two fans.
|
||||
|
||||
The 47M15x and 47M192 chips contain a full 'hardware monitoring block'
|
||||
in addition to the fan monitoring and control. The hardware monitoring
|
||||
block is not supported by the driver.
|
||||
The LPC47M15x, LPC47M192 and LPC47M292 chips contain a full 'hardware
|
||||
monitoring block' in addition to the fan monitoring and control. The
|
||||
hardware monitoring block is not supported by the driver.
|
||||
|
||||
No documentation is available for the 47M997, but it has the same device
|
||||
ID as the 47M15x and 47M192 chips and seems to be compatible therewith.
|
||||
|
||||
@@ -156,8 +156,11 @@ implementations. Please report any other references you have found!</p>
|
||||
<p>
|
||||
As far we know only one motherboard manufacturer provides sensors.conf files:</p>
|
||||
<ul>
|
||||
<li><a href="http://www.tyan.com/support/html/software_utilities.html#lms">TYAN motherboads sensors.conf
|
||||
files database</a></li>
|
||||
<li><a href="http://www.tyan.com/archive/support/html/software_utilities.html#lms">TYAN motherboads sensors.conf
|
||||
files database (archive link)</a></li>
|
||||
<li><a href="ftp://ftp.tyan.com/software/lms/">TYAN motherboads sensors.conf
|
||||
files database (ftp link)</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Personal collections:</p>
|
||||
|
||||
Reference in new issue
Block a user