From ef432cb2ae8b8efbf3ed5878ac2467263cc609dc Mon Sep 17 00:00:00 2001 From: Jean Delvare Date: Sat, 7 Jan 2006 15:45:59 +0000 Subject: [PATCH] Clarify the W83627THF VID documentation. Backport from Linux 2.6, original patch from Mark M. Hoffman. git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3222 7894878c-1315-0410-8ee3-d5d059ff63e0 --- doc/chips/w83627hf | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/doc/chips/w83627hf b/doc/chips/w83627hf index 32205029..53268656 100644 --- a/doc/chips/w83627hf +++ b/doc/chips/w83627hf @@ -77,12 +77,14 @@ If you really want i2c accesses for these Super I/O chips, use the w83781d driver. However this is not the preferred method now that this ISA driver has been developed. -Technically, the w83627thf does not support a VID reading. However, it's -possible or even likely that your mainboard maker has routed these signals -to a specific set of general purpose IO pins (the Asus P4C800-E is one such -board). The w83627thf driver now interprets these as VID. If the VID on -your board doesn't work, first see doc/vid in the lm_sensors package. If -that still doesn't help, email us at lm-sensors@lm-sensors.org. +The w83627_HF_ uses pins 110-106 as VID0-VID4. The w83627_THF_ uses the +same pins as GPIO[0:4]. Technically, the w83627_THF_ does not support a +VID reading. However the two chips have the identical 128 pin package. So, +it is possible or even likely for a w83627thf to have the VID signals routed +to these pins despite their not being labeled for that purpose. Therefore, +the w83627thf driver interprets these as VID. If the VID on your board +doesn't work, first see doc/vid. If that still doesn't help, you may just +ignore the bogus VID reading with no harm done. For further information on this driver, /proc values, etc. see the w83781d driver documentation.