26 May, 2011

1 commit


21 May, 2011

1 commit


20 May, 2011

2 commits


31 Mar, 2011

1 commit


23 Mar, 2011

12 commits

  • This keymap were used for the Hauppauge Black remote controller
    only. It also contains some keycodes not found there. As the
    Hauppauge Black is now part of the hauppauge keymap, just remove
    it.

    Also, remove the modprobe hacks to select between the Gray
    and the Black versions of the remote controller as:
    - Both are supported by default by the keymap;
    - If the user just wants one keyboard supported,
    it is just a matter of changing the keymap via
    the userspace tool (ir-keytable), removing
    the keys that he doesn't desire. As ir-keytable
    auto-loads the keys via udev, this is better than
    obscure modprobe parameters.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • The rc-hauppauge-new map is a messy thing, as it bundles 3

    different remote controllers as if they were just one,
    discarding the address byte. Also, some key maps are wrong.

    With the conversion to the new rc-core, it is likely that
    most of the devices won't be working properly, as the i2c
    driver and the raw decoders are now providing 16 bits for
    the remote, instead of just 8.

    delete mode 100644 drivers/media/rc/keymaps/rc-hauppauge-new.c

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

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

    Mauro Carvalho Chehab
     
  • The keys for the old black were messed with the ones for the
    hauppauge grey. Fix it.

    Also, fixes some keycodes and order the keys according with
    the way they appear inside the remote controller.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • Hans borrowed me an old Black Hauppauge RC. Thanks to that, we
    can fix the RC5 table for Hauppauge.

    Thanks-to: Hans Verkuil
    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • Adds the old grey remote controller to Hauppauge table.

    Hans borrowed me an old gray Hauppauge RC. Thanks to that, we
    can fix the RC5 table for Hauppauge.

    Thanks-to: Hans Verkuil
    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • One of the remotes has a picture available at:
    http://lirc.sourceforge.net/remotes/leadtek/Y04G0004.jpg

    As there's one variant with a set direction keys plus vol/chann
    keys, and the same table is used for both models, change it to
    represent all keys, avoiding the usage of weird function keys.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • Using xev and testing the "Windows" key on a normal keyboard, it
    is mapped as KEY_LEFTMETA. So, as this is the standard code for
    it, use it, instead of a generic, meaningless KEY_PROG1.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • Those KEY_PROG[n] keys were used on places where the developer
    didn't know for sure what key should be used. On several cases,
    using KEY_RED, KEY_GREEN, KEY_YELLOW would be enough. On others,
    there are specific keys for that already.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • Each keyboard map were using a different definition for
    the Source/Video Source key.
    Behold Columbus were the only one using KEY_PROPS.

    As we want to standardize those keys at X11 and at
    userspace applications, we need to use just one code
    for it.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • On a few places, KEY_MHP were used for snapshots. However, KEY_CAMERA
    is used for it on all the other keyboards that have a snapshot/Picture
    button.

    Signed-off-by: Mauro Carvalho Chehab
    Signed-off-by: Jarod Wilson

    Mauro Carvalho Chehab
     
  • These bubble button remote controls appear to be generic from China.

    These are the three variants known to be supplied with DM04/QQBOX DVB-S

    They could well be supplied with other devices from the region.

    Signed-off-by: Malcolm Priestley
    Signed-off-by: Mauro Carvalho Chehab

    Malcolm Priestley
     

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
     

31 Jan, 2011

1 commit


19 Jan, 2011

1 commit


29 Dec, 2010

11 commits