1. 11 1月, 2012 1 次提交
  2. 24 11月, 2011 1 次提交
  3. 22 9月, 2011 3 次提交
  4. 28 7月, 2011 1 次提交
    • J
      [media] rc-core support for Microsoft IR keyboard/mouse · f5f2cc64
      Jarod Wilson 提交于
      This is a custom IR protocol decoder, for the RC-6-ish protocol used by
      the Microsoft Remote Keyboard, apparently developed internally at
      Microsoft, and officially dubbed MCIR-2, per their March 2011 remote and
      transceiver requirements and specifications document, which also touches
      on this IR keyboard/mouse device.
      
      Its a standard keyboard with embedded thumb stick mouse pointer and
      mouse buttons, along with a number of media keys. The media keys are
      standard RC-6, identical to the signals from the stock MCE remotes, and
      will be handled as such. The keyboard and mouse signals will be decoded
      and delivered to the system by an input device registered specifically
      by this driver.
      
      Successfully tested with multiple mceusb-driven transceivers, as well as
      with fintek-cir and redrat3 hardware. Essentially, any raw IR hardware
      with enough sampling resolution should be able to use this decoder,
      nothing about it is at all receiver-hardware-specific.
      
      This work is inspired by lirc_mod_mce:
      
      The documentation there and code aided in understanding and decoding the
      protocol, but the bulk of the code is actually borrowed more from the
      existing in-kernel decoders than anything. I did recycle the keyboard
      keycode table, a few defines, and some of the keyboard and mouse data
      parsing bits from lirc_mod_mce though.
      
      Special thanks to James Meyer for providing the hardware, and being
      patient with me as I took forever to get around to writing this.
      
      callback routine to ensure we don't get any stuck keys, and used
      symbolic names for the keytable. Also cc'ing Florian this time, who I
      believe is the original mod-mce author...
      
      CC: Florian Demski <fdemski@users.sourceforge.net>
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      f5f2cc64
  5. 20 5月, 2011 1 次提交
  6. 23 3月, 2011 1 次提交
    • M
      [media] rc/keymaps: Rename Hauppauge table as rc-hauppauge · 15195d3a
      Mauro Carvalho Chehab 提交于
      There are two "hauppauge-new" keymaps, one with protocol
      unknown, and the other with the protocol marked accordingly.
      However, both tables are miss-named.
      
      Also, the old rc-hauppauge-new is broken, as it mixes
      three different controllers as if they were just one.
      
      This patch solves half of the problem by renaming the
      correct keycode table as just rc-hauppauge. This table
      contains the codes for the four different types of
      remote controllers found on Hauppauge cards, properly
      mapped with their different addresses.
      
       create mode 100644 drivers/media/rc/keymaps/rc-hauppauge.c
       delete mode 100644 drivers/media/rc/keymaps/rc-rc5-hauppauge-new.c
      [Jarod: fix up RC_MAP_HAUPPAUGE defines]
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      15195d3a
  7. 22 3月, 2011 2 次提交
  8. 29 12月, 2010 6 次提交
  9. 23 10月, 2010 2 次提交
  10. 21 10月, 2010 14 次提交
  11. 10 9月, 2010 1 次提交
  12. 09 8月, 2010 1 次提交
    • J
      V4L/DVB: staging/lirc: port lirc_streamzap to ir-core · 8e9e6064
      Jarod Wilson 提交于
      This ports lirc_streamzap.c over to ir-core in-place, to be followed by
      a patch moving the driver over to drivers/media/IR/streamzap.c and
      enabling the proper Kconfig bits.
      
      Presently, the in-kernel keymap doesn't work, as the stock Streamzap
      remote uses an RC-5-like, but not-quite-RC-5 protocol, which the
      in-kernel RC-5 decoder doesn't cope with. The remote can be used right
      now with the lirc bridge driver though, and other remotes (at least an
      RC-6(A) MCE remote) work perfectly with the driver.
      
      I'll take a look at making the existing RC-5 decoder cope with this odd
      duck, possibly implement another standalone decoder engine, or just
      throw up my hands and say "meh, use lirc"... But the driver itself
      should be perfectly sound.
      
      Remaining items on the streamzap TODO list:
      - add LIRC_SET_REC_TIMEOUT-alike support
      - add LIRC_GET_M{AX,IN}_TIMEOUT-alike support
      - add LIRC_GET_REC_RESOLUTION-alike support
      
      All of the above should be trivial to add. There are patches pending to
      add this support to ir-core from Maxim Levitsky, and I'll take care of
      these once his patches get integrated. None of them are currently
      essential though.
      Signed-off-by: NJarod Wilson <jarod@redhat.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      8e9e6064
  13. 03 8月, 2010 5 次提交
  14. 01 6月, 2010 1 次提交