public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Ringel <stefan.ringel@arcor.de>
To: Massis Sirapian <msirapian@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: HVR900H : IR Remote Control
Date: Sun, 14 Nov 2010 16:47:09 +0100	[thread overview]
Message-ID: <4CE0047D.8060401@arcor.de> (raw)
In-Reply-To: <4CDFF446.2000403@free.fr>

  Am 14.11.2010 15:37, schrieb Massis Sirapian:
> Hi,
>
> I have discovered, upgrading my old WinTV PCI Hauppauge card to a 
> HVR-900H USB stick how much the IR userspace has evolved.
>
> I'm using the 2.6.36 kernel provided by Debian in its experimental 
> repository.
>
> Loading the tm6000_dvb works fine (even if it takes a while when I 
> modprobe it while the USB stick is already plugged). Kaffeine sees and 
> uses correctly the device.
>
> However, I'd like to use the IR remote control. It seems to be 
> recognized, as dmesg | grep -i lirc gives :
>
> [  123.306153] lirc_dev: IR Remote Control driver registered, major 250
> [  123.306932] IR LIRC bridge handler initialized
>
> I have no event nor input device created. I've understood from Jarod's 
> pages that the new IR userspace doesn't necessarily require lirc, but 
> sees the IR receiver as a "keyboard". No such device is present in 
> /proc/bus/input/devices
>
> inputlirc + irw don't show anything.
>
> Am I missing something here ? Do I have to load a specific module ?
>
> I have found a lot of information concerning imon, but none I can 
> apply to my HVR-900H/tm6000 case.
>
> Thanks in advance
>
> Massis
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
HVR900H doesn't use lirc. It generates an input device, if a rc_map is 
present for this device.

  reply	other threads:[~2010-11-14 15:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-14 14:37 HVR900H : IR Remote Control Massis Sirapian
2010-11-14 15:47 ` Stefan Ringel [this message]
2010-11-14 19:22   ` Massis Sirapian
2010-11-14 20:49     ` Mariusz Bialonczyk
2010-11-14 22:20       ` Massis Sirapian
2010-11-15  2:28     ` Jarod Wilson
2010-11-15  9:15     ` Richard Zidlicky
2010-11-15 17:43       ` Stefan Ringel
2010-11-15 21:00         ` Massis Sirapian
2010-11-15 21:08           ` Stefan Ringel
2010-11-16 20:26             ` Massis Sirapian
2010-11-16 20:32               ` Stefan Ringel
2010-11-16 20:42                 ` Massis Sirapian
2010-11-16 20:52                   ` Stefan Ringel
2010-11-17 19:33                     ` Massis Sirapian
2010-11-18 19:59                       ` Massis Sirapian
2010-11-18 20:07                         ` Devin Heitmueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CE0047D.8060401@arcor.de \
    --to=stefan.ringel@arcor.de \
    --cc=linux-media@vger.kernel.org \
    --cc=msirapian@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox