1. 03 6月, 2012 1 次提交
    • M
      HID: logitech: don't use stack based dj_report structures · d8dc3494
      Marc Dionne 提交于
      On a system with a logitech wireless keyboard/mouse and DMA-API debugging
      enabled, this warning appears at boot:
      
      kernel: WARNING: at lib/dma-debug.c:929 check_for_stack.part.12+0x70/0xa7()
      kernel: Hardware name: MS-7593
      kernel: uhci_hcd 0000:00:1d.1: DMA-API: device driver maps memory fromstack [addr=ffff8801b0079c29]
      
      Make logi_dj_recv_query_paired_devices and logi_dj_recv_switch_to_dj_mode
      use a structure allocated with kzalloc rather than a stack based one.
      Signed-off-by: NMarc Dionne <marc.c.dionne@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      d8dc3494
  2. 11 5月, 2012 1 次提交
    • J
      HID: logitech: read all 32 bits of report type bitfield · 44d27f7d
      Jonathan Nieder 提交于
      On big-endian systems (e.g., Apple PowerBook), trying to use a
      logitech wireless mouse with the Logitech Unifying Receiver does not
      work with v3.2 and later kernels.  The device doesn't show up in
      /dev/input.  Older kernels work fine.
      
      That is because the new hid-logitech-dj driver claims the device.  The
      device arrival notification appears:
      
      	20 00 41 02 00 00 00 00 00 00 00 00 00 00 00
      
      and we read the report_types bitfield (02 00 00 00) to find out what
      kind of device it is.  Unfortunately the driver only reads the first 8
      bits and treats that value as a 32-bit little-endian number, so on a
      powerpc the report type seems to be 0x02000000 and is not recognized.
      
      Even on little-endian machines, connecting a media center remote
      control (report type 00 01 00 00) with this driver loaded would
      presumably fail for the same reason.
      
      Fix both problems by using get_unaligned_le32() to read all four
      bytes, which is a little clearer anyway.  After this change, the
      wireless mouse works on Hugo's PowerBook again.
      
      Based on a patch by Nestor Lopez Casado.
      Addresses http://bugs.debian.org/671292Reported-by: NHugo Osvaldo Barrera <hugo@osvaldobarrera.com.ar>
      Inspired-by: NNestor Lopez Casado <nlopezcasad@logitech.com>
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NNestor Lopez Casado <nlopezcasad@logitech.com>
      Cc: <stable@vger.kernel.org>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      44d27f7d
  3. 01 5月, 2012 1 次提交
  4. 02 2月, 2012 1 次提交
  5. 20 9月, 2011 1 次提交
  6. 15 9月, 2011 1 次提交
    • N
      HID: Add full support for Logitech Unifying receivers · 534a7b8e
      Nestor Lopez Casado 提交于
      With this driver, all the devices paired to a single Unifying
      receiver are exposed to user processes in separated /input/dev
      nodes.
      
      Keyboards with different layouts can be treated differently,
      Multiplayer games on single PC (like home theater PC) can
      differentiate input coming from different kbds paired to the
      same receiver.
      
      Up to now, when Logitech Unifying receivers are connected to a
      Linux based system, a single keyboard and a single mouse are
      presented to the HID Layer, even if the Unifying receiver can
      pair up to six compatible devices. The Unifying receiver by default
      multiplexes all incoming events (from multiple keyboards/mice)
      into these two.
      Signed-off-by: NNestor Lopez Casado <nlopezcasad@logitech.com>
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      534a7b8e