1. 19 3月, 2013 1 次提交
  2. 14 3月, 2013 1 次提交
  3. 14 2月, 2013 1 次提交
    • C
      [media] media: Add 0x3009 USB PID to ttusb2 driver (fixed diff) · ed72d37a
      Christoph Nuscheler 提交于
      The "Technisat SkyStar USB plus" is a TT-connect S-2400 clone, which the
      V4L-DVB drivers already support. However, some of these devices (like
      mine) come with a different USB PID 0x3009 instead of 0x3006.
      
      There have already been patches simply overwriting the USB PID in
      dvb-usb-ids.h. Of course these patches were rejected because they would
      have disabled the 0x3006 PID.
      
      This new patch adds the 0x3009 PID to dvb-usb-ids.h, and adds references
      to it within the ttusb2.c driver. PID 0x3006 devices will continue to work.
      
      The only difference between the two hardware models seems to be the
      EEPROM chip. In fact, Windows BDA driver names the 0x3009 device with a
      "(8 kB EEPROM)" suffix. In spite of that, the 0x3009 device works
      absolutely flawlessly using the existing ttusb2 driver.
      Signed-off-by: NChristoph Nuscheler <christoph.nuscheler@t-online.de>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ed72d37a
  4. 09 2月, 2013 1 次提交
  5. 06 2月, 2013 2 次提交
  6. 06 1月, 2013 1 次提交
  7. 29 12月, 2012 3 次提交
  8. 28 12月, 2012 12 次提交
  9. 05 12月, 2012 1 次提交
  10. 28 10月, 2012 2 次提交
  11. 27 10月, 2012 1 次提交
    • D
      [media] rc-core: add separate defines for protocol bitmaps and numbers · c003ab1b
      David Härdeman 提交于
      The RC_TYPE_* defines are currently used both where a single protocol is
      expected and where a bitmap of protocols is expected.
      
      Functions like rc_keydown() and functions which add/remove entries to the
      keytable want a single protocol. Future userspace APIs would also
      benefit from numeric protocols (rather than bitmap ones). Keytables are
      smaller if they can use a small(ish) integer rather than a bitmap.
      
      Other functions or struct members (e.g. allowed_protos,
      enabled_protocols, etc) accept multiple protocols and need a bitmap.
      
      Using different types reduces the risk of programmer error. Using a
      protocol enum whereever possible also makes for a more future-proof
      user-space API as we don't need to worry about a sufficient number of
      bits being available (e.g. in structs used for ioctl() calls).
      
      The use of both a number and a corresponding bit is dalso one in e.g.
      the input subsystem as well (see all the references to set/clear bit when
      changing keytables for example).
      
      This patch separate the different usages in preparation for
      upcoming patches.
      
      Where a single protocol is expected, enum rc_type is used; where one or more
      protocol(s) are expected, something like u64 is used.
      
      The patch has been rewritten so that the format of the sysfs "protocols"
      file is no longer altered (at the loss of some detail). The file itself
      should probably be deprecated in the future though.
      Signed-off-by: NDavid Härdeman <david@hardeman.nu>
      Cc: Andy Walls <awalls@md.metrocast.net>
      Cc: Maxim Levitsky <maximlevitsky@gmail.com>
      Cc: Antti Palosaari <crope@iki.fi>
      Cc: Mike Isely <isely@pobox.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      c003ab1b
  12. 06 10月, 2012 2 次提交
  13. 26 9月, 2012 1 次提交
  14. 24 9月, 2012 1 次提交
  15. 14 9月, 2012 1 次提交
  16. 21 8月, 2012 1 次提交
  17. 17 8月, 2012 1 次提交
  18. 14 8月, 2012 3 次提交
新手
引导
客服 返回
顶部