On Fri, 2010-10-22 at 23:39 -0200, Mauro Carvalho Chehab wrote:
> Em 22-10-2010 23:25, Maxim Levitsky escreveu:
> > On Thu, 2010-10-21 at 11:56 -0200, Mauro Carvalho Chehab wrote:
> >> Em 21-10-2010 11:46, Jarod Wilson escreveu:
> >>> On Oct 20, 2010, at 1:18 PM, Mauro Carvalho Chehab wrote:
> >>>
Em 22-10-2010 23:25, Maxim Levitsky escreveu:
> On Thu, 2010-10-21 at 11:56 -0200, Mauro Carvalho Chehab wrote:
>> Em 21-10-2010 11:46, Jarod Wilson escreveu:
>>> On Oct 20, 2010, at 1:18 PM, Mauro Carvalho Chehab wrote:
>>>
The RC5 decoding is complete at a BIT_END state. there's no reason
>>
On Thu, 2010-10-21 at 11:56 -0200, Mauro Carvalho Chehab wrote:
> Em 21-10-2010 11:46, Jarod Wilson escreveu:
> > On Oct 20, 2010, at 1:18 PM, Mauro Carvalho Chehab wrote:
> >
> >> The RC5 decoding is complete at a BIT_END state. there's no reason
> >> to wait for the next space to produce a code.
Em 21-10-2010 11:46, Jarod Wilson escreveu:
> On Oct 20, 2010, at 1:18 PM, Mauro Carvalho Chehab wrote:
>
>> The RC5 decoding is complete at a BIT_END state. there's no reason
>> to wait for the next space to produce a code.
>
> Well, if I'm reading things correctly here, I think the only true fu
On Oct 20, 2010, at 1:18 PM, Mauro Carvalho Chehab wrote:
> The RC5 decoding is complete at a BIT_END state. there's no reason
> to wait for the next space to produce a code.
Well, if I'm reading things correctly here, I think the only true functional
difference made to the decoder here was to s
The RC5 decoding is complete at a BIT_END state. there's no reason
to wait for the next space to produce a code.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/IR/ir-rc5-decoder.c
b/drivers/media/IR/ir-rc5-decoder.c
index df4770d..4139678 100644
--- a/drivers/media/IR/ir-rc