Changeset 1648
- Timestamp:
- 11/26/02 01:59:13 (6 years ago)
- Files:
-
- lm-sensors/trunk/CHANGES (modified) (3 diffs)
- lm-sensors/trunk/doc/chips/SUMMARY (modified) (3 diffs)
- lm-sensors/trunk/doc/chips/bmcsensors (modified) (1 diff)
- lm-sensors/trunk/doc/developers/new_drivers (modified) (3 diffs)
- lm-sensors/trunk/doc/developers/proc (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
lm-sensors/trunk/CHANGES
r1636 r1648 43 43 Module i2c-ipmb: New 44 44 Module i2c-ipmi: New 45 Module i2c-keywest: Sync with kernel 2.4.20 45 46 Module i2c-sis630: Add support for SiS730 46 47 Module i2c-sis645: Improve support for SiS645/961; … … 52 53 Module w83781d: Fix in0/in1 initialization 53 54 Module smartbatt: New 54 Modules (several): Remove #ifndefs, require i2c-2.7.0 55 Modules (several): Remove #ifndefs, require i2c-2.7.0; HZ fixes 55 56 Program decode-dimms.pl: Code cleanup; valid HTML; better HTML output; 56 57 stop decoding on checksum error … … 67 68 initial support for Sony Vaio eeprom 68 69 Program sensors-detect: Add support for MC1066, smart battery, 8235, 69 IPMI, AMD8111; 70 IPMI, AMD8111; add help if no sensors found; 70 71 add ACPI method for IBM system detection; 71 72 work with old Perl versions again; lm-sensors/trunk/doc/chips/SUMMARY
r1614 r1648 132 132 smartbatt 1 1 - - yes no 133 133 134 smsc 74m1135 smsc 74m1 - - 2 2 no yes (LPC)134 smsc47m1 135 smsc47m1 - - 2 2 no yes (LPC) 136 136 137 137 thmc50 … … 145 145 vt1211 146 146 vt1211 2-7 2-7 2 2 no yes (LPC) 147 148 vt8231 149 vt8231 2-7 2-7 2 2 no yes 147 150 148 151 w83781d … … 162 165 Driver Chips 163 166 ------ ----- 167 168 bmcsensors 169 An interface to an IPMI BMC (Baseboard management controller) 164 170 165 171 bt869 lm-sensors/trunk/doc/chips/bmcsensors
r1614 r1648 48 48 The IPMI device interface and IPMI watchdog handler are not required. 49 49 50 You must modprobe i2c-ipmi separately, it will not 51 load automatically when you modprobe bmcsensors. 52 50 53 If the KCS handler (ipmi_kcs_drv) is configured as a module, 51 you must modprobe it separately, it will not load automatically54 you must also modprobe it separately, it will not load automatically 52 55 when you modprobe i2c-ipmi or ipmi_msghandler (unless you set up 53 56 /etc/modules.conf to load ipmi_kcs_drv when ipmi_msghandler is loaded). 57 54 58 55 59 /proc entries lm-sensors/trunk/doc/developers/new_drivers
r1492 r1648 1 1 These are the steps you should follow to write a new driver and 2 2 submit it to us so that it will be applied cleanly to our package. 3 See at the bottom for adding new chip support to an existing driver. 3 4 4 5 Don't be intimidated by the list, it's just here so we don't … … 38 39 Also, please do not use // comments. 39 40 Also, please do not go past column 80. 41 Also, please use C99 struct initializers {.foo = blat} 40 42 Please do this _before_ you check in your driver. 41 43 … … 141 143 * Move .o reference in kernel/[chips,busses]/Module.mk 142 144 from first to second section. 145 146 147 --------------------------------------------------------------------- 148 Checklist for _adding_ support for a chip to an _existing_ driver: 149 150 * Make the changes to the driver itself. 151 152 * Add detection information to prog/detect/sensors-detect. 153 154 * Add a strncmp() call for the new prefix in prog/sensors/main.c 155 (chip drivers only). 156 157 * Add entries for the new prefix to etc/sensors.conf.eg (chip drivers only). 158 159 * Update config help in mkpatch/mkpatch.pl. 160 161 * Update config entry in mkpatch/Config.in (chip drivers only) 162 163 * Update config entry in mkpatch/mkpatch.pl (bus drivers only) 164 165 * Update doc/[chips,busses]/xxx file 166 167 * Update doc/chips/SUMMARY file (chip drivers only) 168 169 * Update list in README 170 171 * Submit the changes as a patch or check them in 172 173 * Update entry on 'new drivers' page 174 lm-sensors/trunk/doc/developers/proc
r1610 r1648 35 35 in the future. 36 36 37 Alarms are direct indications read from the chips. The drivers do NOT make 38 comparisons of readings to thresholds. This allows violations 39 between readings to be caught and alarmed. The exact definition of 40 an alarm (for example, whether a threshold must be met or must be 41 exceeded to cause an alarm) is chip-dependent. 42 37 43 Guidelines for new entries: 38 44 - If there are multiple values, some r/w and some r/o, 39 45 put the r/w ones first. 40 46 - Additional non-standard values should be after the standard values. 47 41 48 42 49 … … 67 74 68 75 curr[1-n] 3 Current max, min or hysteresis, and input value. 69 Floating point values XX X.X or XXX.XX in Amps.76 Floating point values XX.X or XX.XX in Amps. 70 77 The second value is preferably a hysteresis value, 71 78 reported as a absolute current, NOT a delta from
