1. 18 8月, 2012 1 次提交
  2. 27 3月, 2012 2 次提交
  3. 22 3月, 2012 1 次提交
    • S
      toshiba_acpi: Refuse to load on machines with buggy INFO implementations · f11f999e
      Seth Forshee 提交于
      Several Satellite models have a buggy implementation of the INFO method
      that causes ACPI exceptions when executed:
      
       ACPI Error: Result stack is empty! State=ffff88012d70f800 (20110413/dswstate-98)
       ACPI Exception: AE_AML_NO_RETURN_VALUE, Missing or null operand (20110413/dsutils-646)
       ACPI Exception: AE_AML_NO_RETURN_VALUE, While creating Arg 0 (20110413/dsutils-763)
       ACPI Error: Method parse/execution failed [\_SB_.VALZ.GETE] (Node ffff880131175eb0), AE_AML_NO_RETURN_VALUE (20110413/psparse-536)
       ACPI Error: Method parse/execution failed [\_SB_.VALZ.INFO] (Node ffff880131175ed8), AE_AML_NO_RETURN_VALUE (20110413/psparse-536)
       toshiba_acpi: ACPI INFO method execution failed
       toshiba_acpi: Failed to query hotkey event
      
      All known machines with this implementation also have a WMI interface
      with event GUID 59142400-C6A3-40FA-BADB-8A2652834100 which is not seen
      on any other models. Refuse to load toshiba_acpi on machines with this
      guid.
      Signed-off-by: NSeth Forshee <seth.forshee@canonical.com>
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      f11f999e
  4. 21 3月, 2012 5 次提交
  5. 12 3月, 2012 2 次提交
  6. 06 3月, 2012 2 次提交
  7. 18 12月, 2011 1 次提交
  8. 09 11月, 2011 2 次提交
  9. 24 10月, 2011 2 次提交
  10. 28 9月, 2011 1 次提交
    • P
      doc: fix broken references · 395cf969
      Paul Bolle 提交于
      There are numerous broken references to Documentation files (in other
      Documentation files, in comments, etc.). These broken references are
      caused by typo's in the references, and by renames or removals of the
      Documentation files. Some broken references are simply odd.
      
      Fix these broken references, sometimes by dropping the irrelevant text
      they were part of.
      Signed-off-by: NPaul Bolle <pebolle@tiscali.nl>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      395cf969
  11. 06 8月, 2011 1 次提交
  12. 28 5月, 2011 2 次提交
  13. 17 5月, 2011 1 次提交
  14. 09 5月, 2011 1 次提交
  15. 04 5月, 2011 1 次提交
  16. 02 4月, 2011 1 次提交
    • R
      msi-laptop: fix config-dependent build error · a0bcaee9
      Randy Dunlap 提交于
      The msi-laptop driver uses input_*() and sparse_keymap_*() interfaces.
      It should depend on the INPUT subsystem being present and select
      INPUT_SPARSEKMAP so that those interfaces are present.
      
      ERROR: "input_free_device" [drivers/platform/x86/msi-laptop.ko] undefined!
      ERROR: "input_register_device" [drivers/platform/x86/msi-laptop.ko] undefined!
      ERROR: "sparse_keymap_setup" [drivers/platform/x86/msi-laptop.ko] undefined!
      ERROR: "input_allocate_device" [drivers/platform/x86/msi-laptop.ko] undefined!
      ERROR: "sparse_keymap_report_event" [drivers/platform/x86/msi-laptop.ko] undefined!
      ERROR: "input_unregister_device" [drivers/platform/x86/msi-laptop.ko] undefined!
      ERROR: "sparse_keymap_free" [drivers/platform/x86/msi-laptop.ko] undefined!
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: Matthew Garrett <mjg@redhat.com>
      Cc: "Lee, Chun-Yi" <jlee@novell.com>
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      a0bcaee9
  17. 28 3月, 2011 10 次提交
  18. 22 3月, 2011 1 次提交
  19. 22 2月, 2011 1 次提交
    • R
      platform/x86: ideapad-laptop depends on INPUT · ad0f4306
      Randy Dunlap 提交于
      Most platform/x86 drivers that use INPUT_SPARSEKMAP also depend on INPUT,
      so do the same for ideapad-laptop.  This fixes a kconfig warning and
      subsequent build errors when CONFIG_INPUT is disabled.
      
      warning: (ACER_WMI && ASUS_LAPTOP && DELL_WMI && HP_WMI && PANASONIC_LAPTOP && IDEAPAD_LAPTOP && EEEPC_LAPTOP && EEEPC_WMI && MSI_WMI && TOPSTAR_LAPTOP && ACPI_TOSHIBA) selects INPUT_SPARSEKMAP which has unmet direct dependencies (!S390 && INPUT)
      
      ERROR: "input_free_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      ERROR: "input_register_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      ERROR: "sparse_keymap_setup" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      ERROR: "input_allocate_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      ERROR: "input_unregister_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      ERROR: "sparse_keymap_free" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      ERROR: "sparse_keymap_report_event" [drivers/platform/x86/ideapad-laptop.ko] undefined!
      Signed-off-by: NRandy Dunlap <randy.dunlap@oracle.com>
      Cc: David Woodhouse <dwmw2@infradead.org>
      Cc: Matthew Garrett <mjg@redhat.com>
      Cc: platform-driver-x86@vger.kernel.org
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      ad0f4306
  20. 11 1月, 2011 1 次提交
    • M
      platform/x86: Consistently select LEDS Kconfig options · 0c51a4d8
      Mark Brown 提交于
      Currently the x86 platform devices are not consistent about selecting
      or depending on the LEDs Kconfig variables, and this inconsistency
      leads to Kconfig getting upset and refusing to offer LEDs (even on
      non-x86 platforms):
      
      drivers/platform/x86/Kconfig:422:error: recursive dependency detected!
      drivers/platform/x86/Kconfig:422:       symbol EEEPC_WMI depends on ACPI_WMI
      drivers/platform/x86/Kconfig:438:       symbol ACPI_WMI is selected by ACER_WMI
      drivers/platform/x86/Kconfig:18:        symbol ACER_WMI depends on LEDS_CLASS
      drivers/leds/Kconfig:10:        symbol LEDS_CLASS is selected by EEEPC_WMI
      
      Fix this by always selecting rather than depending on the symbols as
      slightly more drivers use this approach already and it seems more
      user friendly.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NMatthew Garrett <mjg@redhat.com>
      0c51a4d8
  21. 08 1月, 2011 1 次提交