- 08 2月, 2008 1 次提交
-
-
由 Jean Delvare 提交于
While it is possible to force SMBus-based hardware monitoring chip drivers to drive a not officially supported device, we do not have this possibility for Super-I/O-based drivers. That's unfortunate because sometimes newer chips are fully compatible and just forcing the driver to load would work. Instead of that we have to tell the users to recompile the kernel driver, which isn't an easy task for everyone. So, I propose that we add a module parameter to all Super-I/O based hardware monitoring drivers, letting advanced users force the driver to load on their machine. The user has to provide the device ID of a supposedly compatible device. This requires looking at the source code or a datasheet, so I am confident that users can't randomly force a driver without knowing what they are doing. Thus this should be relatively safe. As you can see from the code, the implementation is pretty simple and unintrusive. Signed-off-by: NJean Delvare <khali@linux-fr.org> Acked-by: NHans de Goede <j.w.r.degoede@hhs.nl> Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
-
- 10 10月, 2007 3 次提交
-
-
由 Tony Jones 提交于
Convert from class_device to device for hwmon_device_register/unregister Signed-off-by: NTony Jones <tonyj@suse.de> Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de> Signed-off-by: NKay Sievers <kay.sievers@vrfy.org> Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
-
由 Mark M. Hoffman 提交于
Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
-
由 Hans de Goede 提交于
This is the second version of a new driver for the hardware monitoring features of the Fintek F71882FG and F71883FG Super-I/O chips. This version has several small fixes for flaws discovered during the review of the first version. This version of the driver does not support the pwm part of these chips (yet). I'll first design a sysfs api for this and post that for discussion, and then implement pwm support as an incremental patch over this one. This driver supports all sensors of this chip, except for the vid inputs. The vid inputs are somewhat documented in the datasheet, but I know nothing about vid/vrm stuff. Help with this would be much appreciated. Signed-off-by: NHans de Goede <j.w.r.degoede@hhs.nl> Acked-by: NDarrick J. Wong <djwong@us.ibm.com> Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
-