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

Bug#524403: Add support for the IguanaWorks USB IR Transceiver



Hi

Today this patch has been merged into the linux kernel (3.6.0~rc0):

commit 26ff63137c45886169ed102bddd6e90d6c27f00d
Author: Sean Young <sean@mess.org>
Date:   Sun Jul 15 13:31:00 2012 -0300

    [media] Add support for the IguanaWorks USB IR Transceiver
    
    Signed-off-by: Sean Young <sean@mess.org>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=26ff63137c45886169ed102bddd6e90d6c27f00d

While I can not confirm if, or how well it works (no IguanIR hardware),
I'd suggest to give it a try and discuss success/ failure with Debian's
kernel maintainers. Looking through the patch, it should be rather easy
to backport it to kernel 3.2/ wheezy as well (probably no changes 
needed). Therefore I'd suggest to close or reassign src:_linux/ retitle
"please 'Add support for the IguanaWorks USB IR Transceiver'" this
bugreport.

With my lirc maintainer hat, this kernel driver should work as-is, 
configured as dev/input, using the new(ish) RC_CORE subsystem. You
can check the supported IR protocols with:

$ cat /sys/class/rc/rc0/protocols 
rc-5 nec rc-6 jvc sony sanyo mce_kbd [lirc]
[this output is taken from a mceusb device]

The iguanair userspace tools should not be necessary anymore, depending
on your use case even lirc might not be strictly required anymore, as 
the defaults -if left unconfigured- are to expose a normal input 
device.

In case there are problems, an additional follow-up patch has been 
submitted a few days ago[1], but didn't make it into 3.6.0~rc0 yet.

Feel free to contact me/ the lirc maintainer team, if you have problems
with configuring lirc for using this new kernel driver.

Regards
	Stefan Lippers-Hollmann

[1]	http://www.mail-archive.com/linux-media@vger.kernel.org/msg49730.html

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


Reply to: