> Please test the latest version.
This is it! Work fine for me.
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> Return the complete RC-5 code, instead of just the 8 least significant
> bits.
>
> Reported-by: Dorozel Csaba
> Tested-by: Dorozel Csaba
> Signed-off-by: Mauro Carvalho Chehab
>
> ---
>
> Please, re-test this patch. It is a more detailed version of the
&
> Return the complete RC-5 code, instead of just the 8 least significant
> bits.
>
> Reported-by: Dorozel Csaba
> Tested-by: Dorozel Csaba
> Signed-off-by: Mauro Carvalho Chehab
>
> ---
>
> Please, re-test this patch. It is a more detailed version of the
&
> Changing the mask to 0x1fff would work, but this may not be the
> right fix.
>
> the hole idea is that other RC-5 devices could also be used with
> the driver, but if the sub-routine is not doing the right thing, only
> this remote will work.
>
> Could you please try this patch, instead? It i
> An RC-5 code is just 14 bits. I found some Hauppauge decoders returning
> just 12 bits on some places. It seems that all it needs is to do a
> code3 | 0x3f, in order to discard the two most significant bits (MSB).
>
> So, the enclosed patch should fix the issues. Please test.
Half way .. somet
> Basically, the bridge driver is not sending the complete RC-5
> keycode to the IR core, but just the 8 least siginificant bits.
> So, it is loosing the 0x1e00 code for the Hauppauge grey remote.
>
> The fix should be at saa7134-input. It should be something like
> the enclosed patch (I'm just gu
