1. 09 1月, 2011 1 次提交
  2. 25 1月, 2010 1 次提交
  3. 17 12月, 2009 3 次提交
  4. 15 9月, 2009 1 次提交
  5. 28 7月, 2009 1 次提交
  6. 07 1月, 2009 1 次提交
    • J
      hwmon: Check for ACPI resource conflicts · b9acb64a
      Jean Delvare 提交于
      Check for ACPI resource conflicts in hwmon drivers. I've included
      all Super-I/O and PCI drivers.
      
      I've voluntarily left out:
      * Vendor-specific drivers: if they conflicted on any system, this would
        pretty much mean that they conflict on all systems, and we would know
        by now.
      * Legacy ISA drivers (lm78 and w83781d): they only support chips found
        on old designs were ACPI either wasn't supported or didn't deal with
        thermal management.
      * Drivers accessing the I/O resources indirectly (e.g. through SMBus):
        the checks are already done where they belong, i.e. in the bus drivers.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Acked-by: NDavid Hubbard <david.c.hubbard@gmail.com>
      b9acb64a
  7. 17 2月, 2008 1 次提交
  8. 08 2月, 2008 1 次提交
    • J
      hwmon: Let the user override the detected Super-I/O device ID · 67b671bc
      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>
      67b671bc
  9. 10 10月, 2007 2 次提交
  10. 13 8月, 2007 1 次提交
  11. 31 7月, 2007 1 次提交
    • J
      hwmon: Add missing __devexit tags in various drivers · d0546128
      Jean Delvare 提交于
      On Sun, 22 Jul 2007 00:30:56 +0200, Gabriel C wrote:
      > I noticed this warnings on current git:
      >
      > drivers/hwmon/pc87360.c:1082: warning: 'pc87360_remove' defined but not used
      > drivers/hwmon/sis5595.c:580: warning: 'sis5595_remove' defined but not used
      > drivers/hwmon/smsc47m1.c:608: warning: 'smsc47m1_remove' defined but not used
      > drivers/hwmon/via686a.c:648: warning: 'via686a_remove' defined but not used
      > drivers/hwmon/vt8231.c:755: warning: 'vt8231_remove' defined but not used
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NMark M. Hoffman <mhoffman@lightlink.com>
      d0546128
  12. 20 7月, 2007 2 次提交
  13. 08 5月, 2007 5 次提交
  14. 19 10月, 2006 1 次提交
  15. 29 9月, 2006 2 次提交
  16. 27 9月, 2006 1 次提交
  17. 27 6月, 2006 1 次提交
  18. 24 3月, 2006 1 次提交
  19. 06 1月, 2006 2 次提交
  20. 29 10月, 2005 2 次提交
  21. 10 9月, 2005 1 次提交
  22. 06 9月, 2005 6 次提交
  23. 27 8月, 2005 1 次提交
  24. 12 7月, 2005 1 次提交