A few small documentation updates, and an updated example config file

git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@139 7894878c-1315-0410-8ee3-d5d059ff63e0

INSTALL

@@ -101,7 +101,7 @@ Where version 1 of this package had the human-readable /proc/sensors file,
 this version includes a user-space program which gathers all data
 and displays it in a comparable format. This program is called 'sensors'.
 Everybody can use it to read sensors values; only root can use it to
-set minimum and maximum values [NOTE: not yet implemented]
+set minimum and maximum values.
 
 If you want to run 'sensors' without installing the package, you must
 use the following command to make it able to find its shared library:

TODO

@@ -14,7 +14,7 @@ Many, many things. Most notably:
   done for the i2c modules, too.
 * Make lm78.c detect 'double hits', (same chip connected to both SMBus and
   ISA).
-* Better lm78/lm75 detection; insmod-time paramters to set addresses 
+* Better chip detection; insmod-time paramters to set addresses 
   (difficult, because of all i2c busses!).
 * Registrate which i2c addresses are used (a la ISA) for each adapter.
 * Rename i2c-proc.c to i2c-user.c, and extend it with /dev entries;
@@ -26,3 +26,4 @@ Many, many things. Most notably:
 * Write a userland-library for SMBus/i2c access (through the /dev interface)
 * Write a userland detection program for busses (clients are less important;
   but perhaps needed too).
+* Some library routines are pretty inefficient right now

doc/FAQ

@@ -395,10 +395,9 @@ the provided 'sensors' program) instead.
 
 	This is a bit intricate right now. In the near future, this can be
 done through the 'sensors' program, which will take account of the
-computations specified in the configuration file. This will probably not
+computations specified in the configuration file. At this moment, you must
-be implemented in time for 2.1.0, though.
+also put the 'set' commands into the configuration file. This will get
-	At this moment, you have to cat values to /proc/sys/dev/sensors/*/*
+easier in newer versions.
-files, and do any computations by hand. Sorry.
 
 
 4.15 Some sensors are doubly detected?

doc/progs

@@ -20,7 +20,8 @@ this package.
 There are some programs distributed with Simon Vogl's i2c package too:
 * i2c/detect/detect (written in C, not installed)
   This program needs module `i2c-dev.o' to be loaded. It scans the complete
-  address range of a certain bus for connected devices.
+  address range of a certain bus for connected devices. It will only work
+  for i2c-level drivers (not for PIIX4 busses).
 * i2c/eeprom/eeprom (written in C, not installed)
   This program needs the i2c `eeprom.o' module (that is the one that is not
   installed; it can be found in the i2c/drivers/ directory). It reads from

etc/sensors.conf.eg

@@ -95,11 +95,11 @@
 
 # Set statements set things like limits. Complete expressions can be
 # used. Not everything can sensibly be set: setting 'in0', for example,
-# is impossible! These settings # are put through the compute translations;
+# is impossible! These settings are put through the compute translations;
-# so if we specify '12.8' # for in6, '3.2' will actually be written!
+# so if we specify '12.8' for in6, '3.2' will actually be written!
 
-# Though set statements are correctly parsed at this moment, nothing will
+#set in0_max vid*1.05
-# be done with them yet by libsensors
+#set in0_min vid*0.95
 
 # Invalid statements tell certain features are not wanted. User programs can
 # still read them if they really want, though; this is just an advisory
@@ -178,6 +178,23 @@ chip "lm78-*" "lm78-j-*" "lm79-*" "w83781d-*"
     compute in5 -(210/60.4)*@  ,  -@/(210/60.4)
     compute in6 -(90.9/60.4)*@ ,  -@/(90.9/60.4)
 
+# Here, we assume the VID readings are valid, and we use a max. 5% deviation
+
+    set in0_min vid*0.95
+    set in0_max vid*1.05
+    set in1_min vid*0.95
+    set in1_max vid*1.05
+    set in2_min 3.3 * 0.95
+    set in2_max 3.3 * 1.05
+    set in3_min 5.0 * 0.95
+    set in3_max 5.0 * 1.05
+    set in4_min 12 * 0.95
+    set in4_max 12 * 1.05
+    set in5_min -12 * 0.95
+    set in5_max -12 * 1.05
+    set in6_min -5 * 0.95
+    set in6_max -5 * 1.05
+
 
 chip "gl518sm-r00-*" "gl518sm-r80-*"
 
@@ -229,3 +246,20 @@ chip "lm80-*"
     compute in4 (160/35.7 + 1) * @,       @ / (160/35.7 + 1)
     compute in5 (160/35.7)*(@ - in0) + @, (@ + in0 * 160/25.7)/ (1 + 160/25.7)
     compute in6 (36/16.2)*(@ - in0) + @,  (@ + in0 * 36/16.2) / (1 + 36/16.2)
+
+    set in0_min 5 * 0.95
+    set in0_max 5 * 0.95
+# What is your VTT? It is probably not this value...
+    set in1_min 2*0.95
+    set in1_max 2*1.05
+    set in2_min 3.3 * 0.95
+    set in2_max 3.3 * 1.05
+# What is your VCore? It is probably not this value...
+    set in3_min 1.9 * 0.95
+    set in3_max 1.9 * 1.05
+    set in4_min 12 * 0.95
+    set in4_max 12 * 1.05
+    set in5_min -12 * 0.95
+    set in5_max -12 * 1.05
+    set in6_min -5 * 0.95
+    set in6_max -5 * 1.05