On Tue, Jul 27, 2010 at 7:32 PM, Maxim Levitsky <maximlevitsky@xxxxxxxxx> wrote:
> On Wed, 2010-07-28 at 01:33 +0300, Maxim Levitsky wrote:
>> Hi,
>>
>> I ported my ene driver to in-kernel decoding.
>> It isn't yet ready to be released, but in few days it will be.
>>
>> Now, knowing about wonders of in-kernel decoding, I try to use it, but
>> it just doesn't work.
>>
>> Mind you that lircd works with this remote.
>> (I attach my lircd.conf)
>>
>> Here is the output of mode2 for a single keypress:
8850 4350 525 1575 525 1575
525 450 525 450 525 450
525 450 525 1575 525 450
525 1575 525 450 525 1575
525 450 525 450 525 1575
525 450 525 450 525 23625
That decodes as:
1100 0010 1010 0100
In the NEC protocol the second word is supposed to be the inverse of
the first word and it isn't. The timing is too short for NEC protocol
too.
Valid NEC...
1100 0011 1010 0101
Maybe JVC protocol but it is longer than normal.
The JVC decoder was unable to get started decoding it. I don't think
the JVC decoder has been tested much. Take a look at it and see why it
couldn't get out of state 0.
>
> Just want to add that I tested it with many different modes of my
> remotes, and all but one fail (one mode is detected as NEC).
>
> Don't get me wrong.
> Although I opposed to idea of in-kernel decoding, lately I began to
> think that this isn't such a bad idea.
> Especially if number of users for whom it will work out of box.
>
> So, I am very disappointed.
>
> Best regards,
> Maxim Levitsky
>
>
--
Jon Smirl
jonsmirl@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
