[mythtv-users] Need help with mce usb remote control

[Jarod Wilson]

On Wed, Jun 16, 2010 at 8:22 PM, Brent Bolin <brent.bolin at gmail.com> wrote:
> On Wed, Jun 16, 2010 at 4:46 PM, Jarod Wilson <jarod at wilsonet.com> wrote:
>>
>> On Wed, Jun 16, 2010 at 1:27 PM, nospam312 <nospam312 at gmail.com> wrote:
>> >> replaced by a new mceusb driver... :)
>> >
>> > Is there any further information on this?  Is it a drop in replacement
>> > or a more substantial change breaking setups that have worked for
>> > years?
>>
>> Both. Its a new driver written for the new ir-core infrastructure
>> we've been working on upstream. Default out of the box experience is
>> that the bundled RC6 remotes Just Work via the linux input layer --
>> i.e., they work without any lirc configuration work as well as without
>> even having lirc installed (we use an in-kernel RC6 IR decoder, then
>> pass along decoded key values via the input layer).
>>
>> However, I've also written an ir-core to lirc_dev bridge driver that
>> allows you to use the device with lirc like you always have. To do
>> that, you'd probably want to disable the in-kernel decoding though --
>> which is as simple as echoing a value into /sys/class/rc/rcX/protocols
>> (there's some flux as to whether there will be protocol-specific
>> nodes, or a single node for all protocols, which you echo the protocol
>> name into...). I've got four different mceusb transceivers and several
>> remotes that all work perfectly with both in-kernel decoding and lirc
>> bridge mode (including transmit support). The fun can all be seen
>> here:
>>
>> http://git.wilsonet.com/linux-2.6-ir-wip.git/?a=shortlog;h=refs/heads/patches
>>
>
> Are you saying when you have a device like this shown in
> /var/log/messages hid device
>
>
> Jun 15 11:46:12 brent kernel: [   12.184174] generic-usb
> 0003:147A:E03C.0002: timeout initializing reports
> Jun 15 11:46:12 brent kernel: [   12.184595] generic-usb
> 0003:147A:E03C.0002: hiddev96,hidraw1: USB HID v1.00 Device [Formosa21
> eHome Infrared Transceiver] on usb-0000:00:04.0-5/input1
>
> That you don't need to be using lircd?

I'm saying that in the future, any device currently supported by
lirc_mceusb will not actually require lirc to be useful.

-- 
Jarod Wilson
jarod at wilsonet.com