[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Pkg-lirc-maint] LIRC 0.9 backport to go with backported Linux kernel?


On Monday 16 April 2012, Stefan Lippers-Hollmann wrote:
> On Sun, 15 Apr 2012 23:39:03 +0100, Ben Hutchings wrote
> > On Sun, 2012-04-15 at 23:47 +0200, Stefan Lippers-Hollmann wrote:
> > > On Sunday 15 April 2012, Josh Triplett wrote:
> […]
> > > > Would you consider providing a backport of LIRC 0.9 for squeeze?

Small error corrections inline.

> **************************************************************
> * IR remotes indistinguishably emulating USB keyboard/ mouse *
> **************************************************************
> Yes, even these exist - and are "nice" to configure…
> Usually you require inputlirc, in order to get exclusive access to the 
> event device and to avoid getting spurious key presses. Once more
> udev rules, several this time, will be required:
> SUBSYSTEM=="input",ATTRS{idVendor}=="05a4",ATTRS{idProduct}=="9881",IMPORT{program}="input_id %p"
> SUBSYSTEM=="input",ATTRS{idVendor}=="05a4",ATTRS{idProduct}=="9881",ENV{ID_INPUT_KEYBOARD}=="1",SYMLINK="input/irremote0"
> SUBSYSTEM=="input",ATTRS{idVendor}=="05a4",ATTRS{idProduct}=="9881",ENV{ID_INPUT_MOUSE}=="1",SYMLINK="input/irremote1"
> lircd.conf can be "random".

well, not "random", but specific to this particular device, whose vendor might indeed have given a monkey the task of inventing keycodes, after restoring Sakespeare from /dev/random.

> ***********************************************************************
> An additional hurdle, some of these devices only work with their 
> bundled IR remote, while others can be paired with very different ones,
> as long as the IR frequency matches roughly or the employed RC_CORE
> protocols are matching.

you will need to generate a custom lircd.conf for these - or 
create ir_keytable mappings, depending on your actual device.

> ***********************************************************************


> [ That said, lirc is -in most cases- not a critical functionality, this 
>   means you can boot any kernel version you like - lircd's init script 
>   might "just" error out and your IR remote won't work, until you boot 
>   into a supported kernel. It will 


>   make booting fail or totally break 
>   the system ]


	Stefan Lippers-Hollmann

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply to: