Changeset 1492
- Timestamp:
- 08/15/02 04:40:47 (6 years ago)
- Files:
-
- lm-sensors/trunk/CHANGES (modified) (1 diff)
- lm-sensors/trunk/doc/FAQ (modified) (3 diffs)
- lm-sensors/trunk/doc/developers/genpasswd.pl (modified) (1 diff)
- lm-sensors/trunk/doc/developers/new_drivers (modified) (4 diffs)
- lm-sensors/trunk/doc/progs (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
lm-sensors/trunk/CHANGES
r1490 r1492 38 38 Program sensors: Add /usr/local/etc to config file path; 39 39 fix -c and -u flags 40 Program sensors-detect: recognize Asus "ASB100 Bach" as AS99127F 40 Program sensors-detect: recognize Asus "ASB100 Bach" as AS99127F; 41 refuse to run on IBM systems 41 42 42 43 2.6.4 (20020719) lm-sensors/trunk/doc/FAQ
r1443 r1492 100 100 4.29 Inserting modules hangs my board 101 101 4.30 Inserting modules slows down my board 102 4.31 Problems on particular motherboards 103 4.31A Asus P4B 104 4.31B Tyan 2460, 2462 105 4.31C Tyan 2466 106 4.31D Tyan 2688 102 107 103 108 5. How to Ask for Help … … 949 954 3) The sensors it has are on an I2C bus connected to an 950 955 I2C bus adapter that we don't support. 956 4) You don't have the latest version of lm_sensors. 951 957 But in any case you should figure out what is on the board: 952 958 1) Look at your motherboard. … … 1034 1040 temperature limits are above the temperature reading. Put 1035 1041 the new limits in /etc/sensors.conf and run 'sensors -s'. 1042 1043 1044 4.31 Problems on particular motherboards 1045 1046 The following boards have unique problems and solutions. 1047 1048 1049 4.31A Asus P4B 1050 1051 See prog/hotplug/README.p4b if your SMBus master is not found. 1052 1053 1054 4.31B Tyan 2460, 2462 1055 1056 See support tickets 805, 765, 781, 812, 813, and 867 for information. 1057 1058 1059 4.31C Tyan 2466 1060 1061 See support tickets 941, 840, and 841 for information. 1062 1063 1064 4.31D Tyan 2688 1065 1066 For board hangs, see support ticket 721 for information. 1067 Also see #4.29 5) above. 1036 1068 1037 1069 lm-sensors/trunk/doc/developers/genpasswd.pl
r1160 r1492 30 30 print "Please specify whether you want access to i2c, lm_sensors, or both.\n"; 31 31 print "Please also indicate what area of the project you wish to work on.\n"; 32 print "\n"; 33 print "Please include your username in the CVS comments when you\n"; 34 print "check in files like so: (username)\n"; lm-sensors/trunk/doc/developers/new_drivers
r1453 r1492 17 17 i2c-id.h in the i2c package. 18 18 Tell us it's OK to put your name on the "New Drivers" page. 19 Ask to be put on the mailing list so you get project updates. 19 20 20 21 * Check out our latest code from CVS. … … 39 40 Please do this _before_ you check in your driver. 40 41 42 * Add sysctl definitions to kernel/include/sensors.h (for chip drivers only). 43 These define the entries in the ctl_table for /proc. 44 41 45 * Meet /proc naming standards in the ctl_table (for chip drivers only). 42 46 See doc/developers/proc for information. 43 47 44 * Add the driver to the Module.mk ( makefile).48 * Add the driver to the Module.mk (the makefile). 45 49 Usually, you can just add it to KERNEL{CHIPS,DRIVERS}TARGETS in the 46 Module.mk file in the directory itself. 50 Module.mk file in the directory itself. Put it at the beginning, 51 where the comment says to put drivers NOT included in mkpatch. 47 52 48 53 * Make sure it compiles cleanly. … … 90 95 * Add your name to the CONTRIBUTORS file. 91 96 92 * Add entries to the CHANGES file. 97 * Add entries to the CHANGES file. Please keep in alphabetical order. 93 98 94 99 * Write a doc/chips/xxx or doc/busses/xxx file. … … 99 104 new driver so we know you are giving it to us under the GPL. 100 105 101 * Submit the changes to us. 102 Check out a clean version of CVS again (things will have changed since 103 you started), then submit the changes to us as a patch against CVS. 106 * Get CVS write access if you want to check in your driver yourself. 107 Do this by running the script doc/developers/genpasswd.pl and following 108 the instructions it gives you. 109 110 * Submit the changes to us, or check them in. 111 Do a 'cvs update' to get in sync (things will have changed since 112 you started), then submit the changes to us as a patch against CVS, 113 or check them in. 104 114 105 115 --------------------------------------------------------------------- lm-sensors/trunk/doc/progs
r1415 r1492 25 25 An example of a very simple hardware health monitoring daemon. 26 26 27 * prog/detect/i2cdetect (written in C, not installed) 27 * prog/detect/dmidecode (written in C, installed by 'make install') 28 This program scans the DMI (Desktop Management Interface) information 29 in the BIOS and prints out the useful information. 30 31 * prog/detect/i2cdetect (written in C, installed by 'make install') 28 32 This program scans your complete I2C or SMBus adapter for connected devices. 29 33 Not all devices can be detected in this way, though; and it may hang your … … 52 56 ./doc-insmod.pl DRIVER 53 57 54 * prog/dump/i2cdump (written in C, not installed)58 * prog/dump/i2cdump (written in C, installed by 'make install') 55 59 This program dumps the registers of a I2C device that understands 56 60 the 'byte data' or 'word data' and block read SMBus protocols. … … 62 66 or word data. 63 67 64 * prog/dump/i2cset (written in C, not installed)68 * prog/dump/i2cset (written in C, installed by 'make install') 65 69 This program is used to write the register of a I2C device. 66 70 Usual syntax: 67 71 ./i2cset bus device address data 68 72 69 * prog/dump/isadump (written in C, not installed)73 * prog/dump/isadump (written in C, installed by 'make install') 70 74 This program dumps the registers of LM78-like chips, or more 71 75 exactly, chips which use one I/O-port for its address and one as its
