Re: Bug or a faulty devise?

[Jarod W. <ja...@wi...>]

On Mar 3, 2011, at 1:20 AM, Kris jensen wrote:

> On Wed, 2011-03-02 at 22:39 -0500, Kris jensen wrote:
>> On Wed, 2011-03-02 at 10:55 -0500, Jarod Wilson wrote:
>>> On Mar 1, 2011, at 1:06 PM, Kris jensen wrote:
>>> 
>>>> Hello,
>>>> I have a mceusb transceiver (model # AVS Gear GP-IR02BK). That is
>>>> working for both receiving and transmitting in Ubuntu 10.10 and with
>>>> LIRC (0.8.7~pre3-0ubuntu1) using the kernels built in module “mceusb”  
>>>> 
>>>> So I bought another one of the same make and model. I had some problems
>>>> getting the second transceiver fully working so I returned it for a
>>>> replacement, thinking it was faulty.
>>>> 
>>>> However the replacement is doing the same thing. It can receive signals
>>>> fine but well not send signals.
>>>> The only differences I see between the two are: 
>>>> 
>>>> (On working transceiver.)
>>>> 
>>>> ~$ lsusb
>>>> Bus 004 Device 003: ID 1784:0008 TopSeed Technology Corp. eHome Infrared
>>>> Transceiver
>>>> 
>>>> The other transceiver that is not working for transmitting
>>> 
>>> ...
>>>> ~$ lsusb
>>>> Bus 004 Device 003: ID 1784:0011 TopSeed Technology Corp.
>>>> 
>>>> What’s going on here? I hope that my luck is not just that bad to have
>>>> two bad devises one after the other.  But I kind of doubt it. Seeing
>>>> that it receives ok.
>>> 
>>> If I had to guess, I'd say the 0011 device type might not be correct
>>> in the driver. It either doesn't have an inverted tx mask like its
>>> currently marked, or it needs the gen3 init sequence like the 0008
>>> does to function properly. Testing out either of those possibilities
>>> is relatively easy, but does require use of the linuxtv media_build
>>> infra to properly test.
>>> 
>>> http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
>>> 
>> Thanks Jarod,
>> 
>> Ok, I've installed V4L-DVB Device_Drivers. I would like to help with the
>> test please =)
>> 
>> However, I consider myself a Linux noob with good google skills. So that
>> being said, if I seem to go all glossy eyed and your patients is wearing
>> thin I'll understand.
>> 
>> Thanks again,
>> 
>> 
> Well, I read a bit deeper in to your reply and poked about. looked in to
> the media_build directory, found mceusb.c, found the line for my devise
> and changed it from "driver_info = MCE_GEN2_TX_INV" To "driver_info =
> MCE_GEN3"

Yep, that's exactly what I was going to suggest trying. That, and/or
just removing the driver_info setting altogether (defaulting to plain
gen2).


> And it works.

Perfect, I'll push a patch to make that change.


> Thanks Jarod =)

No problem, thanks for testing.

-- 
Jarod Wilson
ja...@wi...