From: Filippo Argiolas <filippo.argiolas@gmail.com>
To: Matthew Vermeulen <mattvermeulen@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] [patch] support for key repeat with dib0700 ir receiver
Date: Wed, 20 Feb 2008 09:27:48 +0100 [thread overview]
Message-ID: <1203496068.7026.19.camel@tux> (raw)
In-Reply-To: <1203495773.7026.15.camel@tux>
Il giorno mer, 20/02/2008 alle 09.22 +0100, Filippo Argiolas ha scritto:
> Il giorno mer, 20/02/2008 alle 06.10 +0900, Matthew Vermeulen ha
> scritto:
> > 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...
>
> Are you sure that the input device is receiving the events?
> Did you try evtest /dev/input/event7?
> Is LIRC properly configured?
> Are you using this file for lircd.conf
> [http://linux.bytesex.org/v4l2/linux-input-layer-lircd.conf]?
> Does irw catch some event?
I forgot to say to not use irrecord with dev/input driver since it's
thinked to record raw events from remotes and doesn't work with input
devices (usually it ends up with a lircd.conf file that interprets key
press and release as separated events doubling each event).
Just use the proper input-layer-lircd.conf.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-02-20 8:27 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 15:17 [linux-dvb] [patch] support for key repeat with dib0700 ir receiver Filippo Argiolas
2008-02-19 17:21 ` Nicolas Will
2008-02-19 17:30 ` Filippo Argiolas
2008-02-19 19:19 ` Nicolas Will
2008-02-19 19:30 ` Nicolas Will
2008-02-19 21:10 ` Matthew Vermeulen
2008-02-19 22:09 ` Nicolas Will
2008-02-20 7:39 ` Matthew Vermeulen
2008-02-20 7:54 ` Nicolas Will
2008-02-20 13:10 ` Matthew Vermeulen
2008-02-20 8:22 ` Filippo Argiolas
2008-02-20 8:27 ` Filippo Argiolas [this message]
2008-02-20 12:36 ` Matthew Vermeulen
2008-02-20 13:23 ` Nicolas Will
2008-02-20 13:43 ` Matthew Vermeulen
2008-02-20 14:15 ` Filippo Argiolas
[not found] ` <1203517472.6682.37.camel@acropora>
2008-02-20 20:09 ` Patrik Hansson
2008-02-20 22:57 ` Matthew Vermeulen
2008-02-20 23:08 ` Matthew Vermeulen
2008-02-20 8:22 ` Filippo Argiolas
2008-02-19 21:14 ` Patrick Boettcher
2008-02-19 21:41 ` Jonas Anden
2008-02-19 22:16 ` Nicolas Will
2008-02-19 22:29 ` Patrick Boettcher
2008-02-19 22:50 ` hermann pitton
2008-02-20 4:18 ` Supported device? Lyal Collins
2008-02-19 22:52 ` [linux-dvb] [patch] support for key repeat with dib0700 ir receiver Nicolas Will
2008-02-20 9:00 ` Jonas Anden
2008-02-20 2:05 ` Darren Salt
2008-02-20 9:27 ` Filippo Argiolas
2008-02-20 9:39 ` Nicolas Will
2008-02-20 10:06 ` Filippo Argiolas
2008-03-02 19:45 ` Filippo Argiolas
2008-03-10 22:17 ` Nicolas Will
2008-02-27 11:04 ` Nicolas Will
-- strict thread matches above, loose matches on Subject: below --
2008-02-19 16:33 Eduard Huguet
2008-02-19 16:49 ` Filippo Argiolas
2008-02-19 17:07 ` Eduard Huguet
[not found] <mailman.77.1203547335.926.linux-dvb@linuxtv.org>
2008-02-21 9:54 ` Eduard Huguet
2008-02-21 15:42 ` Filippo Argiolas
2008-02-22 10:56 ` Matthew Vermeulen
2008-02-22 11:07 ` Nicolas Will
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=1203496068.7026.19.camel@tux \
--to=filippo.argiolas@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=mattvermeulen@gmail.com \
/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