From: Petr Baudis <pasky@suse.cz>
To: "José Suárez" <j.suarez.agapito@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
Michael Krufky <mkrufky@linuxtv.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-dvb@linuxtv.org,
linux-kernel <linux-kernel@vger.kernel.org>,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>
Subject: Re: [linux-dvb] Avermedia 777 misbehaves after remote hack merged into v4l-dvb tree
Date: Tue, 14 Nov 2006 05:28:53 +0100 [thread overview]
Message-ID: <20061114042853.GF18879@pasky.or.cz> (raw)
In-Reply-To: <200611140445.30269.j.suarez.agapito@gmail.com>
On Tue, Nov 14, 2006 at 04:45:29AM CET, José Suárez wrote:
> At the moment I can't give the remote control a try because lirc doesn't
> compile against version 2.6.18 of the kernel. If that lirc issue gets solved,
> I will try to use it as soon as I can.
Note that in lircd, you should use the input device driver
("devinput"). The saa7134 driver will create a random input event device
for the events; I use this udev rule to create a /dev/remote symlink
pointing at the right device:
KERNEL="event*", SYSFS{name}="saa7134 IR*", NAME="input/%k", SYMLINK="remote"
Furthermore, especially if you have problems with lircd, having the
full-blown daemon for the event interface may not be worth it. There is
a standalone inputlircd package containing a much simpler daemon which
is compatible with lirc client applications but takes the events just
from the input devices. You can run it e.g. like:
/usr/sbin/inputlircd /dev/remote -g -m 0
You can find an example mplayer lirc configuration at:
http://pasky.or.cz/~pasky/dev/v4l/lircrc
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next prev parent reply other threads:[~2006-11-14 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611131711.46626.j.suarez.agapito@gmail.com>
2006-11-13 16:32 ` Michael Krufky
2006-11-13 16:44 ` Linus Torvalds
2006-11-13 21:09 ` Michael Krufky
2006-11-13 21:23 ` Mauro Carvalho Chehab
2006-11-14 3:45 ` José Suárez
2006-11-14 4:28 ` Petr Baudis [this message]
2006-11-13 21:17 ` Petr Baudis
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=20061114042853.GF18879@pasky.or.cz \
--to=pasky@suse.cz \
--cc=j.suarez.agapito@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mkrufky@linuxtv.org \
--cc=torvalds@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
/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
all inboxes | Powered by JetHome®