[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1259422559.18747.6.camel@maxim-laptop>
Date: Sat, 28 Nov 2009 17:35:59 +0200
From: Maxim Levitsky <maximlevitsky@...il.com>
To: Krzysztof Halasa <khc@...waw.pl>
Cc: Stefan Richter <stefanr@...6.in-berlin.de>,
Jon Smirl <jonsmirl@...il.com>,
Christoph Bartelmus <christoph@...telmus.de>,
jarod@...sonet.com, awalls@...ix.net, dmitry.torokhov@...il.com,
j@...nau.net, jarod@...hat.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
mchehab@...hat.com, superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel
IR system?
On Sat, 2009-11-28 at 16:25 +0100, Krzysztof Halasa wrote:
> Maxim Levitsky <maximlevitsky@...il.com> writes:
>
> >> And that's good. Especially for a popular and simple protocol such as
> >> RC5.
> >> Actually, it's not about adding the decoder. It's about fixing it.
> >> I can fix it.
> >
> > This is nonsense.
>
> You forgot to say why do you think so.
Because frankly, I am sick of this discussion.
Generic decoder that lirc has is actually much better and more tolerant
that protocol specific decoders that you propose,
You claim you 'fix' the decoder, right?
But what about all these lirc userspace drivers?
How they are supposed to use that 'fixed' decoder.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists