[mythtv-users] Call for iMON testing
Jarod Wilson
jarod at wilsonet.com
Sun Sep 6 20:39:22 UTC 2009
On 09/06/2009 02:58 PM, Christian Szpilfogel wrote:
> Jarod Wilson wrote:
>>> This is all a bit strange but I went back to double check and my Antext
>>> Fusion Black 430 is definitely reporting:
>>> Bus 001 Device 003: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
>>>
>>> and it definitely is only accepting RC-6 codes on mine. It is running
>>> linux with lircd 0.8.3-CVS-pvr150-2 (which is what Knoppmyth bundles in).
>>>
> Actually I was running 0.8.4a. I believe I updated it to get lcd_proc.
>>
>> Hrm. Interesting. Perhaps the ffdc actually *can* be put into either
>> imon or rc6 protocol mode, its just done differently than on the newer
>> devices. That, or you actually *do* have tx control endpoints on your
>> ffdc device, which is entirely possible. SoundGraph made the entirely
>> sucktastic decision to use the ffdc device ID for a LOT of different
>> devices, wasn't until recently they got a clue... Can you try to load
>> lirc_imon with debug=1 and see what all spits out? Curious to see what
>> all is reported about yours...
>>
>>
> ok. With lirc 0.8.4a (what I have on this production front end at the
> moment) I did the following:
0.8.4a output isn't so interesting, its definitely wrong in some places,
really need to see what current cvs thinks it sees. There's been a TON
of change since then.
Regardless, in reading over the code, it seems there's no way your
device has control endpoints, and the linux driver uses the tx control
endpoint to change IR protocols on the fly. So either the older ffdc
devices can have their IR protocol set via some other means, or they're
hard-coded to either imon's native proto or to RC6 from the factory.
--
Jarod Wilson
jarod at wilsonet.com
More information about the mythtv-users
mailing list