Re: [FIXED] Re: lirc on Debian with AMD64
- From: Andrew Sackville-West <andrew@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 1 Oct 2007 10:07:00 -0700
On Mon, Oct 01, 2007 at 12:04:28AM -0400, Brad Sawatzky wrote:
On Sat, 29 Sep 2007, Greg Vickers wrote:
OK, I found out that Debian Etch uses a new input layer, and that the IR
inputs are in /dev/input/eventX where X corresponds the event number of
your input devices in 'cat /proc/bus/input/devices'
So my IR device is /dev/input/event1, instead of /dev/lirc or /dev/lirc0.
Just a heads-up, that event number could easily change from boot to boot.
You can preserve your sanity by making a udev rule like the following and
put it (or a symlink) in "/etc/udev/rules.d/"
KERNEL=="event[0-9]", ATTRS{name}=="cx88 IR *", SYMLINK+="lirc%n"
my udev-fu is very weak, but the %n substitutes the kernel supplied
number. in which case you'll get lirc[0-9] depending on which event it
matches. If you only have one ir port that you care about, then you'd
probably always want it to be the *same* symlink regardless of which
event it gets assigned to:
KERNEL=="event[0-9]", ATTRS{name}=="cx88 IR *", SYMLINK+="lirc0"
A
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: [FIXED] Re: lirc on Debian with AMD64
- From: Brad Sawatzky
- Re: [FIXED] Re: lirc on Debian with AMD64
- References:
- Re: [FIXED] Re: lirc on Debian with AMD64
- From: Brad Sawatzky
- Re: [FIXED] Re: lirc on Debian with AMD64
- Prev by Date: Re: Gnome Update Manager's "Smart" Update
- Next by Date: Re: FLOSS support for signed PDFs
- Previous by thread: Re: [FIXED] Re: lirc on Debian with AMD64
- Next by thread: Re: [FIXED] Re: lirc on Debian with AMD64
- Index(es):
Relevant Pages
|
|