misc updates

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

CHANGES

@@ -37,7 +37,8 @@ ask CVS about it:
                    update chip support, still behind sensors
   Program sensors: Add /usr/local/etc to config file path;
                    fix -c and -u flags
-  Program sensors-detect: recognize Asus "ASB100 Bach" as AS99127F
+  Program sensors-detect: recognize Asus "ASB100 Bach" as AS99127F;
+                          refuse to run on IBM systems
 
 2.6.4 (20020719)
   NOTE: Requires i2c-2.6.1 or newer, or kernel 2.4.13 or newer.

doc/FAQ

@@ -99,6 +99,11 @@ CONTENTS
 4.28 Sensors doesn't find any sensors, just eeproms
 4.29 Inserting modules hangs my board
 4.30 Inserting modules slows down my board
+4.31 Problems on particular motherboards
+  4.31A Asus P4B
+  4.31B Tyan 2460, 2462
+  4.31C Tyan 2466
+  4.31D Tyan 2688
 
 5. How to Ask for Help  
 5.1 What to do if a module won't insert?
@@ -948,6 +953,7 @@ Run devfs in the kernel to get the /dev/i2c/x files.
 	2) We don't support the sensors on the board.
 	3) The sensors it has are on an I2C bus connected to an
 	   I2C bus adapter that we don't support.
+	4) You don't have the latest version of lm_sensors.
     But in any case you should figure out what is on the board:
 	1) Look at your motherboard.
 	2) Check the manufacturer's website.
@@ -1035,6 +1041,32 @@ temperature limits are above the temperature reading. Put
 the new limits in /etc/sensors.conf and run 'sensors -s'.
 
 
+4.31 Problems on particular motherboards
+
+    The following boards have unique problems and solutions.
+
+
+4.31A Asus P4B
+
+    See prog/hotplug/README.p4b if your SMBus master is not found.
+
+
+4.31B Tyan 2460, 2462
+
+    See support tickets 805, 765, 781, 812, 813, and 867 for information.
+
+
+4.31C Tyan 2466
+
+    See support tickets 941, 840, and 841 for information.
+
+
+4.31D Tyan 2688
+
+    For board hangs, see support ticket 721 for information.
+Also see #4.29 5) above.
+
+
 5 How to ask for help
 ---------------------
 

doc/developers/genpasswd.pl

@@ -29,3 +29,6 @@ print "Send this encrypted password to phil\@netroedge.com\n";
 print "with your requested username.\n";
 print "Please specify whether you want access to i2c, lm_sensors, or both.\n";
 print "Please also indicate what area of the project you wish to work on.\n";
+print "\n";
+print "Please include your username in the CVS comments when you\n";
+print "check in files like so: (username)\n";

doc/developers/new_drivers

@@ -16,6 +16,7 @@ Steps which apply to only one type of driver are noted.
   You will also need to ask us to have an ID reserved in
   i2c-id.h in the i2c package.
   Tell us it's OK to put your name on the "New Drivers" page.
+  Ask to be put on the mailing list so you get project updates.
 
 * Check out our latest code from CVS.
   You should use this as a base for your development.
@@ -38,12 +39,16 @@ Steps which apply to only one type of driver are noted.
   Also, please do not go past column 80.
   Please do this _before_ you check in your driver.
 
+* Add sysctl definitions to kernel/include/sensors.h (for chip drivers only).
+  These define the entries in the ctl_table for /proc.
+
 * Meet /proc naming standards in the ctl_table (for chip drivers only).
   See doc/developers/proc for information.
 
-* Add the driver to the Module.mk (makefile).
+* Add the driver to the Module.mk (the makefile).
   Usually, you can just add it to KERNEL{CHIPS,DRIVERS}TARGETS in the
-  Module.mk file in the directory itself.
+  Module.mk file in the directory itself. Put it at the beginning,
+  where the comment says to put drivers NOT included in mkpatch.
 
 * Make sure it compiles cleanly.
   If you compile with 'make WARN=1', you usually get many additional
@@ -89,7 +94,7 @@ Steps which apply to only one type of driver are noted.
 
 * Add your name to the CONTRIBUTORS file.
 
-* Add entries to the CHANGES file.
+* Add entries to the CHANGES file. Please keep in alphabetical order.
 
 * Write a doc/chips/xxx or doc/busses/xxx file.
 
@@ -98,9 +103,14 @@ Steps which apply to only one type of driver are noted.
   (or if applicable your company's name) is at the top of the
   new driver so we know you are giving it to us under the GPL.
 
-* Submit the changes to us.
-  Check out a clean version of CVS again (things will have changed since
-  you started), then submit the changes to us as a patch against CVS.
+* Get CVS write access if you want to check in your driver yourself.
+  Do this by running the script doc/developers/genpasswd.pl and following
+  the instructions it gives you.
+
+* Submit the changes to us, or check them in.
+  Do a 'cvs update' to get in sync (things will have changed since
+  you started), then submit the changes to us as a patch against CVS,
+  or check them in.
 
 ---------------------------------------------------------------------
 Checklist for us to do on the webpage:

doc/progs

@@ -24,7 +24,11 @@ see useful_addresses.html.
 * prog/daemon/healthd.sh (written in bash, not installed)
   An example of a very simple hardware health monitoring daemon.
 
-* prog/detect/i2cdetect (written in C, not installed)
+* prog/detect/dmidecode (written in C, installed by 'make install')
+  This program scans the DMI (Desktop Management Interface) information
+  in the BIOS and prints out the useful information.
+
+* prog/detect/i2cdetect (written in C, installed by 'make install')
   This program scans your complete I2C or SMBus adapter for connected devices.
   Not all devices can be detected in this way, though; and it may hang your
   bus. Syntax:
@@ -51,7 +55,7 @@ see useful_addresses.html.
   all module information and outputs insmod parameter information. Syntax:
     ./doc-insmod.pl DRIVER
 
-* prog/dump/i2cdump (written in C, not installed)
+* prog/dump/i2cdump (written in C, installed by 'make install')
   This program dumps the registers of a I2C device that understands
   the 'byte data' or 'word data' and block read SMBus protocols.
   Usual syntax:
@@ -61,12 +65,12 @@ see useful_addresses.html.
   '0x49' is the device address, and 'b' or 'w' stands for byte
   or word data.
 
-* prog/dump/i2cset (written in C, not installed)
+* prog/dump/i2cset (written in C, installed by 'make install')
   This program is used to write the register of a I2C device.
   Usual syntax:
     ./i2cset bus device address data
 
-* prog/dump/isadump (written in C, not installed)
+* prog/dump/isadump (written in C, installed by 'make install')
   This program dumps the registers of LM78-like chips, or more
   exactly, chips which use one I/O-port for its address and one as its
   data register. Usual syntax: