summary refs log tree commit diff
path: root/Documentation/hwmon/f71805f
diff options
context:
space:
mode:
authorJean Delvare <khali@linux-fr.org>2007-07-15 10:36:06 +0200
committerMark M. Hoffman <mhoffman@lightlink.com>2007-10-09 22:56:28 -0400
commit9cab0217f3f35bd618363842576867badb72ca4b (patch)
tree5731aa857c7b1648cbc6d72ddd1b48fc583d517e /Documentation/hwmon/f71805f
parent43e61a2d7e2ce70a093df83871a436732bc48125 (diff)
downloadlinux-9cab0217f3f35bd618363842576867badb72ca4b.tar.gz
hwmon: (f71805f) List the F71806F/FG as supported
The Fintek F71806F/FG is compatible with the F71872F/FG, so it is
already supported by the f71805f hardware monitoring driver. In fact,
both chips have the same chip ID, so the driver can't even
differentiate between them.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Acked-by: Hans de Goede <j.w.r.degoede@hhs.nl>
Signed-off-by: Mark M. Hoffman <mhoffman@lightlink.com>
Diffstat (limited to 'Documentation/hwmon/f71805f')
-rw-r--r--Documentation/hwmon/f71805f7
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/hwmon/f71805f b/Documentation/hwmon/f71805f
index 94e0d2cbd3d2..f0d55976740a 100644
--- a/Documentation/hwmon/f71805f
+++ b/Documentation/hwmon/f71805f
@@ -6,6 +6,10 @@ Supported chips:
     Prefix: 'f71805f'
     Addresses scanned: none, address read from Super I/O config space
     Datasheet: Available from the Fintek website
+  * Fintek F71806F/FG
+    Prefix: 'f71872f'
+    Addresses scanned: none, address read from Super I/O config space
+    Datasheet: Available from the Fintek website
   * Fintek F71872F/FG
     Prefix: 'f71872f'
     Addresses scanned: none, address read from Super I/O config space
@@ -38,6 +42,9 @@ The Fintek F71872F/FG Super I/O chip is almost the same, with two
 additional internal voltages monitored (VSB and battery). It also features
 6 VID inputs. The VID inputs are not yet supported by this driver.
 
+The Fintek F71806F/FG Super-I/O chip is essentially the same as the
+F71872F/FG, and is undistinguishable therefrom.
+
 The driver assumes that no more than one chip is present, which seems
 reasonable.