1. 29 12月, 2010 1 次提交
  2. 03 8月, 2010 3 次提交
  3. 09 3月, 2010 1 次提交
  4. 27 2月, 2010 1 次提交
  5. 04 12月, 2009 1 次提交
  6. 12 9月, 2009 3 次提交
    • M
      V4L/DVB (12600): dvb-usb-remote: return KEY_RESERVED if there's free space for new keys · a4c1cbc7
      Mauro Carvalho Chehab 提交于
      The input subsystem checks if get_keycode works for a scan code. Due to that,
      we need to return a valid value when there's some space at the table that
      can be used by a scancode.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      a4c1cbc7
    • M
      V4L/DVB (12599): dvb-usb-remote: Allow dynamically replacing the IR keycodes · b77f0a76
      Mauro Carvalho Chehab 提交于
      Implements handler for EVIOCGKEYCODE/EVIOCSKEYCODE via adding two new callbacks
      to the input device.
      
      Since on dvb-usb a scan code has 16 bits, to fulfill rc5 standard codes, the default
      getkeycode/setkeycode input methods would require the driver to spend up to 64 Kb of
      a sparse table. Instead, add two new callbacks to the event device.
      
      With this, it is now possible to replace the keycode tables. There are, however, a few
      implementation details at the current patch:
      
      1) It will replace the existing device keytable, instead of creating an instance
      of the data. This works. However, if two devices pointing to the same table
      were connected, changing the IR table of one will also change the IR table for
      the other (the solution for this one is simple: just kmalloc some memory);
      
      2) In order to change the scan code, you need first to change the key to
      KEY_RESERVED or KEY_UNKNOWN to free some space at the table (solution: allocate
      some additional space for newer scan codes or allow dynamic table grow);
      
      3) The table size cannot be extended. It would be easy to allow the table to
      grow dynamically: just calling kmalloc(size+1); kfree(old). Yet, maybe we can
      just create a bigger table with a fixed size, like for example a table with 128
      entries. This should be enough even for a very big IR.
      
      The current issues should be addressed on a later patch.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      b77f0a76
    • M
      V4L/DVB (12598): dvb-usb: store rc5 custom and data at the same field · 2e365883
      Mauro Carvalho Chehab 提交于
      In order to be closer to V4L IR implementation, it is needed to replace
      	u8 custom, data
      to:
      	u16 scan
      
      This allows using non-rc5 mappings, like the 8 bit keycodes used on older
      protocols. It will also allow future implementations of rc6 keystrokes
      when needed.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      2e365883
  7. 20 10月, 2007 1 次提交
  8. 19 7月, 2007 1 次提交
  9. 09 5月, 2007 1 次提交
  10. 14 4月, 2007 1 次提交
  11. 21 2月, 2007 1 次提交
  12. 10 12月, 2006 1 次提交
  13. 22 11月, 2006 1 次提交
  14. 04 10月, 2006 1 次提交
  15. 26 9月, 2006 1 次提交
  16. 29 10月, 2005 1 次提交
  17. 08 7月, 2005 2 次提交
  18. 24 6月, 2005 1 次提交