[linux-dvb] [patch] support for key repeat with dib0700 ir receiver
mattvermeulen at gmail.com
Wed Feb 20 14:10:17 CET 2008
On Feb 20, 2008 4:54 PM, Nicolas Will <nico at youplala.net> wrote:
> On Wed, 2008-02-20 at 16:39 +0900, Matthew Vermeulen wrote:
> > On Feb 20, 2008 7:09 AM, Nicolas Will <nico at youplala.net> wrote:
> > On Wed, 2008-02-20 at 06:10 +0900, Matthew Vermeulen wrote:
> > > Hi all... I'm seeing exactly the same problems everyone else
> > is (log
> > > flooding etc) except that I can't seem to get any keys
> > picked by lirc
> > > or /dev/input/event7 at all...
> > >
> > > Would this patch help in this case?
> > It would help with the flooding, most probably, though there
> > was a patch
> > for that available before.
> > As for LIRC not picking up the event, I would be tempted to
> > say no, it
> > won't help.
> > Are you certain that your LIRC is configured properly? Are you
> > certain
> > that your event number is the right one?
> > Nico
> > I believe so... in so far as I can tell... I sent an email to this
> > list about a week ago describing my problems, but there was no
> > response. (subject: Compro Videomate U500). I've copied it below:
> > Hi all,
> > I've still been trying to get the inluded remote with my USB DVB-T
> > Tuner working. It's a Compro Videomate U500 - it useses the dibcom
> > 7000 chipset. After upgrading to Ubuntu 8.04 (hardy) I can now see the
> > remote when I do a "cat /proc/bus/input/devices":
> > I: Bus=0003 Vendor=185b Product=1e78 Version=0100
> > N: Name="IR-receiver inside an USB DVB receiver"
> > P: Phys=usb-0000:00:02.1-4/ir0
> > S: Sysfs=/devices/pci0000:00/0000 :00:02.1/usb1/1-4/input/input7
> > U: Uniq=
> > H: Handlers=kbd event7
> > B: EV=3
> > B: KEY=10afc332 2842845 0 0 0 4 80018000 2180 40000801 9e96c0 0 800200
> > ffc
> You went through all this, I guess:
> And you are running a recent v4l-dvb tree, I assume.
> > However, I get now output running irrecord:
> I was never too lucky with irrecord on my system, IIRC.
Ok - just thought I'd try the patch on the latest tree and see what
happens... as expected, it put an end to the syslog flooding - but nothing
really has improved... I still see a single error line in the syslog every
time I press a key - so obviously the kernel is seeing something happen, but
deciding it's unknown and not taking it any further. Something must be wrong
with some mappings somewhere.. :S Here's the syslog output anyway - there is
one line for every key press:
Feb 20 22:07:07 matthew-desktop kernel: [38161.388548] dib0700: Unknown
remote controller key: 12 7E 1 0
Feb 20 22:07:09 matthew-desktop kernel: [38162.678839] dib0700: Unknown
remote controller key: 18 7C 1 0
Feb 20 22:07:10 matthew-desktop kernel: [38162.906413] dib0700: Unknown
remote controller key: 18 7C 1 0
Feb 20 22:07:14 matthew-desktop kernel: [38165.183338] dib0700: Unknown
remote controller key: 1C 4D 1 0
Feb 20 22:07:18 matthew-desktop kernel: [38167.156040] dib0700: Unknown
remote controller key: 1F 7D 1 0
Feb 20 22:07:21 matthew-desktop kernel: [38168.598632] dib0700: Unknown
remote controller key: 19 43 1 0
This is very annoying because it seems that polling the syslog every 150ms
might even give you something if you could work it out ;) Anyway.. any ideas
where to now...?
MatthewV @ irc.freenode.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the linux-dvb