1. 30 1月, 2007 1 次提交
    • J
      HID: fix pb_fnmode and move it to generic HID · 76398f96
      Jiri Kosina 提交于
      The apple powerbook people are used to switch the pb_fnmode
      setting at runtime through writing to sysfs, altering the
      module parameter value. This was broken for them in 2.6.20-rc1
      when generic HID layer was introduced, as the pb_fnmode flag
      was made per-hiddevice, instead of global variable.
      
      This patch moves the pb_fnmode module parameter from usbhid module
      to hid module, but apart from that retains backward compatibility
      with respect to changing the mode through sysfs.
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      76398f96
  2. 26 1月, 2007 1 次提交
  3. 22 1月, 2007 2 次提交
    • J
      HID: hid/hid-input.c doesn't need to include linux/usb/input.h · 1f3ab013
      Jiri Kosina 提交于
      There is no reason for generic hid-input.c to include usb-specific
      input.h.
      
      As a sideeffect, this also fixes warning of redefinition of dbg()
      macro, when hid-input.c is compiled with DEBUG (as there is a clash
      between dbg() from hid.h and usb/input.h).
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      1f3ab013
    • S
      HID: proper LED-mapping for SpaceNavigator · d4ae650a
      Simon Budig 提交于
      This change introduces a mapping for LED indicators between the HID
      specification and the Linux input subsystem. The previous code properly
      mapped the LEDs relevant for Keyboards, but garbeled the remaining ones.
      With this change all LED enums from the input system get mapped to more
      or less equivalent LED numbers from the HID specification.
      
      This patch also ensures that the unused bits in a HID report to the
      device are zeroed out. This makes the 3Dconnexion SpaceNavigator fully
      usable with the linux input system.
      Signed-off-by: NSimon Budig <simon@budig.de>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      d4ae650a
  4. 08 1月, 2007 1 次提交
  5. 14 12月, 2006 1 次提交
  6. 09 12月, 2006 4 次提交
  7. 17 11月, 2006 1 次提交
    • O
      USB: correct keymapping on Powerbook built-in USB ISO keyboards · bb7eef6e
      Olaf Hering 提交于
      similar to the version in adbhid_input_register(): The '<>' key and the
      '^°' key on a german keyboard is swapped.  Provide correct keys to
      userland, external USB keyboards will not work correctly when the
      'badmap'/'goodmap' workarounds from xkeyboard-config are used.
      
      It is expected that distributions drop the badmap/goodmap part from
      keycodes/macintosh in the xkeyboard-config package.
      
      This is probably 2.6.18.x material, if major distros settle on 2.6.18.
      Signed-off-by: NOlaf Hering <olh@suse.de>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      bb7eef6e
  8. 05 11月, 2006 1 次提交
    • A
      Input: HID - add a quirk for the Logitech USB Receiver · 41ad5fba
      Anssi Hannula 提交于
      Logitech USB Receiver (046d:c101) has two interfaces. The first one
      contains fields from HID_UP_KEYBOARD and HID_UP_LED, and the other one
      contains fields from HID_UP_CONSUMER and HID_UP_LOGIVENDOR. This device
      is used with multiple wireless Logitech products, including UltraX Media
      Remote.
      
      All fields on both interfaces are either keys or leds. All fields in the
      first interface are marked as Absolute, while the fields in the second
      interface are marked as Relative. Marking the keys as relative causes
      hidinput_hid_event() to send release events right after key press
      events.
      
      The device has EV_REP set, so the userspace expects the device to send
      repeat events if a key is held down. However, as hidinput_hid_event()
      sends release events immediately, repeat events are not sent at all. In
      fact, the userspace has no way of knowing if a key is being held down.
      
      Fix this by adding a quirk for 046d:c101 which changes relative keys to
      absolute ones.
      Signed-off-by: NAnssi Hannula <anssi.hannula@gmail.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      41ad5fba
  9. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  10. 19 7月, 2006 2 次提交
  11. 15 7月, 2006 1 次提交
  12. 22 6月, 2006 2 次提交
    • D
      [PATCH] USB: move <linux/usb_input.h> to <linux/usb/input.h> · ae0dadcf
      David Brownell 提交于
      Move <linux/usb_input.h> to <linux/usb/input.h> and remove some
      redundant includes.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      ae0dadcf
    • B
      [PATCH] USB HID/HIDBP, INPUT DRIVERS: fix various usb/input/hid-input.c bugs... · a82e49b8
      Bart Massey 提交于
      [PATCH] USB HID/HIDBP, INPUT DRIVERS: fix various usb/input/hid-input.c bugs that make Apple Mighty Mouse work poorly
      
      Transposed lines of code in drivers/usb/input/hid-input.c causes the
      capability bits for a new HID device to be set before quirks are applied
      at configuration time.  When an HID event is then sent up to the input
      layer, it may then be discarded as irrelevant because the wrong
      capability bit is set.
      
      Further, the quirks for the Apple Mighty Mouse are not quite right: the
      horizontal scrolling needs its axis reversed, and the left and center
      buttons are transposed.  Also, the mouse is labeled in the kernel with
      its earlier name (I think) of Apple PowerMouse.
      
      Steps to reproduce problem: Plug in an Apple Mighty Mouse.  Note that
      horizontal scrolling doesn't work at all, and in fact doesn't generate
      any input events on /dev/input/eventN.  Note also that pushing the
      middle button performs the right button action, and vice versa.  Once
      you have the horizontal scrolling working, note that it is backward WRT
      both to vertical scrolling and to common sense.
      
      This patch maybe should be broken up, as it does address two problems.
      The transposed code in hidinput_configure_usage() probably creates bugs
      beyond just the Mighty Mouse.  The rest of the patch renames POWERMOUSE
      to MIGHTYMOUSE everywhere (which I *believe* is correct), fixes the
      MIGHTYMOUSE quirk to swap the center and right mouse buttons, and adds a
      new quirk HID_QUIRK_INVERT_HWHEEL also assigned to the MIGHTYMOUSE with
      code in hidinput_hid_event() to implement it.
      Signed-off-by: NBart Massey <bart@cs.pdx.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      a82e49b8
  13. 14 3月, 2006 1 次提交
  14. 14 1月, 2006 3 次提交
  15. 05 1月, 2006 1 次提交
  16. 19 12月, 2005 1 次提交
  17. 29 10月, 2005 1 次提交
  18. 05 9月, 2005 6 次提交
  19. 30 7月, 2005 1 次提交
  20. 30 6月, 2005 1 次提交
  21. 29 5月, 2005 1 次提交
  22. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4