1. 21 1月, 2011 2 次提交
  2. 18 1月, 2011 5 次提交
  3. 11 1月, 2011 2 次提交
  4. 08 1月, 2011 2 次提交
  5. 07 1月, 2011 5 次提交
  6. 30 12月, 2010 1 次提交
  7. 28 12月, 2010 3 次提交
  8. 23 12月, 2010 3 次提交
  9. 22 12月, 2010 3 次提交
  10. 20 12月, 2010 2 次提交
    • H
      Input: fix double equality sign in uevent · fcd3027a
      Henrik Rydberg 提交于
      Looking at the uevent stream for input devices, all properties are on
      the form "A=B" except the bitmap values, which are on the form
      "A==B". This bug has been around at least since 2007, and the input
      uevent code has been untouched since. The recent addition of device
      properties suggests this is a good time for a remedy.
      Acked-by: NDmitry Torokhov <dtor@mail.ru>
      Signed-off-by: NHenrik Rydberg <rydberg@euromail.se>
      fcd3027a
    • H
      Input: introduce device properties · 85b77200
      Henrik Rydberg 提交于
      Today, userspace sets up an input device based on the data it emits.
      This is not always enough; a tablet and a touchscreen may emit exactly
      the same data, for instance, but the former should be set up with a
      pointer whereas the latter does not need to. Recently, a new type of
      touchpad has emerged where the buttons are under the pad, which
      changes logic without changing the emitted data. This patch introduces
      a new ioctl, EVIOCGPROP, which enables user access to a set of device
      properties useful during setup. The properties are given as a bitmap
      in the same fashion as the event types, and are also made available
      via sysfs, uevent and /proc/bus/input/devices.
      Acked-by: NPing Cheng <pingc@wacom.com>
      Acked-by: NChase Douglas <chase.douglas@canonical.com>
      Acked-by: NDmitry Torokhov <dtor@mail.ru>
      Signed-off-by: NHenrik Rydberg <rydberg@euromail.se>
      85b77200
  11. 18 12月, 2010 1 次提交
  12. 16 12月, 2010 11 次提交