Changes between Version 9 and Version 10 of Kernel2.6
- 05/14/07 20:02:09 (7 years ago)
v9 v10 50 50 Please review this list before reporting a problem to us. 51 51 52 * Some popular chip drivers are not yet ported. Therefore sensors-detect may recommend a driver that is not present. Please check your kernel configuration and the drivers/i2c/chips (up to 2.6.13-rc2) or drivers/hwmon (since 2.6.13-rc3) directory for the presence of your driver. Our [wiki:Devices Devices page] shows which drivers are present in 2.6 kernels. 53 * Following drivers have been ported and should show up in the Linux kernel tree soon: max6650 52 * . 53 * 54 54 * Ports for the following drivers are somewhat underway: bmcsensors, lm93, mtp008 and thmc50 55 55 * If you would like to port an I2C/SMBus hardware monitoring driver, read [http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/i2c/porting-clients Documentation/i2c/porting-clients] as found in the Linux 2.6 kernel source tree. If you would like to port a non-I2C chip driver, make it a platform driver, using the f71805f driver as an example. … … 61 61 Please review this list before reporting a problem to us. 62 62 63 * ASB100 support was dropped from the w83781d driver in Linux 2.6.5 / lm_sensors 2.8.5. If you have an Asus board and w83781d was detecting an AS99127F chip before, but not anymore, you most likely need to use the new, dedicated asb100 driver instead. 63 * . 64 64 * Up to Linux 2.6.10 (included), via686a and i2c-viapro cannot both be loaded due to PCI resource conflicts. For most users, use i2c-isa + via686a to access sensor data. If values don't make sense, unload both drivers and try i2c-viapro + another chip driver (sensors-detect should tell you which). The issue was finally solved in Linux 2.6.11. 65 65 * i2c-voodoo3 generally will not load due to PCI resource conflicts with tdfxfb or other frame buffer / display drivers. The 2.6 driver requests the PCI device, because it is considered Bad (TM) to use a device without requesting it. This probably means that the i2c-voodoo3 driver should me merged into the framebuffer driver, much like was done for matroxfb, radeonfb and nvidiafb. This also makes sense because the framebuffer driver can use the DDC channel (which is no more than I2C, renamed) to retrieve information about the monitor and adapt its output. But this also raises the problem that people may want to access the i2c busses without loading the full framebuffer driver... … … 86 86 Specific issues (all fixed in later versions): 87 87 88 88 89 * VRM is broken for 2.6 kernels in lm_sensors 2.8.6. 89 90 * Hysteresis temperature is broken for 2.6 lm75, lm78 and gl518sm chip drivers in lm_sensors 2.8.6.