11 Jan, 2012

1 commit

  • This remote was added with support for card Compro VideoMate M1F.

    This remote is shipped with various Compro cards, not this one only.

    Furthermore this remote can be bought separately under name Compro
    VideoMate K100.
    http://compro.com.tw/en/product/k100/k100.html

    So give it a proper name.

    [mchehab@redhat.com: Fix the Makefile]
    Signed-off-by: Samuel Rakitničan
    Signed-off-by: Mauro Carvalho Chehab

    Samuel Rakitnican
     

24 Nov, 2011

1 commit


22 Sep, 2011

3 commits


28 Jul, 2011

1 commit

  • 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
    Signed-off-by: Jarod Wilson
    Signed-off-by: Mauro Carvalho Chehab

    Jarod Wilson
     

20 May, 2011

1 commit


23 Mar, 2011

1 commit

  • 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: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     

22 Mar, 2011

2 commits

  • Remote used for TerraTec Cinergy T Stick RC.
    Keytable from Martin Groszhauser

    Signed-off-by: Antti Palosaari
    Cc: Martin Groszhauser
    Cc: TerraTux
    Signed-off-by: Mauro Carvalho Chehab

    Antti Palosaari
     
  • This patch is adding support for Technisat's new USB2.0 DVB-S/S2 receiver
    device. The development was sponsored by Technisat.

    The Green led is toggle depending on the frontend-state. The Red LED is turned
    on all the time.

    The MAC address reading from the EEPROM along with the
    LRC-method to check whether its valid.

    Support for the IR-receiver of the Technisat USB2 box. The keys of
    small, black remote-control are built-in, repeated key behaviour are
    simulated.

    The i2c-mutex of the dvb-usb-structure is used as a general mutex for
    USB requests, as there are 3 threads racing for atomic requests
    consisting of multiple usb-requests.

    A module option is there which disables the toggling of LEDs by the
    driver on certain triggers. Useful when being used in a "dark"
    environment.

    [mchehab@redhat.com: Fix merge conflicts with RC renaming patches]
    Signed-off-by: Martin Wilks
    Signed-off-by: Patrick Boettcher
    Signed-off-by: Mauro Carvalho Chehab

    Patrick Boettcher
     

29 Dec, 2010

6 commits

  • Signed-off-by: Pavel Osnova
    Signed-off-by: Ramiro Morales
    Signed-off-by: Mauro Carvalho Chehab

    Ramiro Morales
     
  • Signed-off-by: Mauro Carvalho Chehab

    Mauro Carvalho Chehab
     
  • Signed-off-by: Mauro Carvalho Chehab

    Mauro Carvalho Chehab
     
  • Remote keytables had different names all over the place. Part of the fault
    is due to a bad naming when rc subsystem was created, but there were lots
    of old names that were still here.

    Use a common standard for everything.

    Patch generated by this script:

    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_scancode,rc_map_table,g a && mv a $i; done
    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_codes_,rc_map_,g a && mv a $i; done
    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,rc_key_map,rc_map_table,g a && mv a $i; done
    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,rc_map_table_size,rc_map_size,g a && mv a $i; done

    Signed-off-by: Mauro Carvalho Chehab

    Mauro Carvalho Chehab
     
  • The struct that describes a rc mapping had an weird and long name.
    We should properly name it, to make easier for developers to work
    with it, and to avoid confusion.

    Basically, generated by this script:

    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_scancode_table,rc_map,g a && mv a $i; done
    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,rc_tab,rc_map,g a && mv a $i; done

    (and manually fixed where needed)

    Signed-off-by: Mauro Carvalho Chehab

    Mauro Carvalho Chehab
     
  • for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,IR_TYPE,RC_TYPE,g a && mv a $i; done
    for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_type,rc_type,g a && mv a $i; done

    Signed-off-by: Mauro Carvalho Chehab

    Mauro Carvalho Chehab
     

29 Oct, 2010

1 commit

  • * 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6: (505 commits)
    [media] af9015: Fix max I2C message size when used with tda18271
    [media] IR: initialize ir_raw_event in few more drivers
    [media] Guard a divide in v4l1 compat layer
    [media] imon: fix nomouse modprobe option
    [media] imon: remove redundant change_protocol call
    [media] imon: fix my egregious brown paper bag w/rdev/idev split
    [media] cafe_ccic: Configure ov7670 correctly
    [media] ov7670: allow configuration of image size, clock speed, and I/O method
    [media] af9015: support for DigitalNow TinyTwin v3 [1f4d:9016]
    [media] af9015: map DigitalNow TinyTwin v2 remote
    [media] DigitalNow TinyTwin remote controller
    [media] af9015: RC fixes and improvements
    videodev2.h.xml: Update to reflect the latest changes at videodev2.h
    [media] v4l: document new Bayer and monochrome pixel formats
    [media] DocBook/v4l: Add missing formats used on gspca cpia1 and sn9c2028
    [media] firedtv: add parameter to fake ca_system_ids in CA_INFO
    [media] tm6000: fix a macro coding style issue
    tm6000: Remove some ugly debug code
    [media] Nova-S-Plus audio line input
    [media] [RFC,1/1] V4L2: Use new CAP bits in existing RDS capable drivers
    ...

    Linus Torvalds
     

23 Oct, 2010

2 commits


21 Oct, 2010

14 commits


10 Sep, 2010

1 commit


09 Aug, 2010

1 commit

  • 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: Jarod Wilson
    Signed-off-by: Mauro Carvalho Chehab

    Jarod Wilson
     

03 Aug, 2010

5 commits