Drop stray references to procfs interface.

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

doc/chips/MODPARMS

@@ -1,5 +1,10 @@
 Parameters for modprobe and insmod
 ==================================
+
+PRELIMINARY WARNING:
+This documentation file is outdated and needs to be entirely reviewed
+and updated. Until then, don't blindly trust what you read here.
+
 ==================================
 SUMMARY
 
@@ -36,15 +41,16 @@ add parameters. Check 'dmesg' for clues to what went wrong.
 BUS NUMBERING
 -------------
 I2C/SMBus adapters are numbered in the order they are inserted. If you want
-to know what number an adapter has, please make sure module `i2c-proc' is 
-inserted, and look at file /proc/bus/i2c. The ISA bus always has the
-symbolic number 9191 (`I' is the ninth letter of the alphabet, `S' the
-nineteenth and `A' the first). Do not use the ISA Bus number from
-/proc/bus/i2c. If you want 'any I2C bus', use '-1' (or 65535).
-So to summarize:
-	-1	Any Bus
-	0-15	Specific I2C Bus
-	9191	ISA BUS
+to know what number an adapter has, use the following command:
+
+  grep . /sys/class/i2c-adapter/i2c-*/name
+
+Alternatively, if you have installed i2c-tools, you can do:
+
+  modprobe i2c-dev
+  i2cdetect -l
+
+If you want 'any I2C bus', use '-1'.
 
 
 ADDRESS NUMBERING

doc/fancontrol.txt

@@ -100,9 +100,9 @@ VARIABLE2=[...]
 
 Each variable has its own line. The variable name is followed by an equal sign
 and the device=value pairs. These consist of the relative path to the pwm
-output (from /proc/sys/dev/sensors, /sys/bus/i2c/devices or /sys/class/hwmon
-depending on the kernel version) for which the value is valid, equal sign
-followed by the value and are separated by a blank.
+output (from /sys/bus/i2c/devices or /sys/class/hwmon depending on the kernel
+version) for which the value is valid, equal sign followed by the value and
+are separated by a blank.
 
 Example:
 

doc/progs

@@ -56,8 +56,7 @@ see http://www.lm-sensors.org/wiki/UsefulLinks.
 * prog/sensors/sensors (written in C, installed by `make install')
   This pretty-prints the information provided by the modules. It is a normal
   console application, using stdout. It is essential, because
-  unlike the raw /proc/sys/dev/sensors/*/* files, it takes your configuration
-  file into account.
+  unlike the raw sysfs files, it takes your configuration file into account.
 
 * prog/tellerstats/gather.sh, tellerstats.sh (written in bash, not installed)
   These scripts gather sensors data and graph the data for web pages.

lib/data.h

@@ -25,7 +25,7 @@
 #include "sensors.h"
 
 /* This header file contains all kinds of data structures which are used
-   for the representation of the config file data and the /proc/...
+   for the representation of the config file data and the sensors
    data. */
 
 /* Kinds of expression operators recognized */
@@ -156,7 +156,7 @@ extern int sensors_proc_bus_max;
 	(el), &sensors_proc_bus, &sensors_proc_bus_count,\
 	&sensors_proc_bus_max, sizeof(struct sensors_bus))
 
-/* Substitute configuration bus numbers with real-world /proc bus numbers
+/* Substitute configuration bus numbers with real-world bus numbers
    in the chips lists */
 int sensors_substitute_busses(void);
 

prog/pwm/fancontrol.8

@@ -1,4 +1,4 @@
-.TH FANCONTROL 8 "June 2007" "lm-sensors 3"
+.TH FANCONTROL 8 "January 2009" "lm-sensors 3"
 .SH NAME
 fancontrol \- automated software based fan speed regulation
 
@@ -82,7 +82,7 @@ VARIABLE2=...
 .PP
 Each variable has its own line. The variable name is followed by an equal sign
 and the device=value pairs. These consist of the relative path to the pwm
-output (from /proc/sys/dev/sensors, /sys/bus/i2c/devices or /sys/class/hwmon
+output (from /sys/bus/i2c/devices or /sys/class/hwmon
 depending on the kernel version) for which the value is valid, equal sign
 followed by the value and are separated by a blank. Example:
 .IP