[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BDZb9P9ZjFB@christoph>
Date: 25 Nov 2009 18:20:00 +0100
From: lirc@...telmus.de (Christoph Bartelmus)
To: khc@...waw.pl
Cc: superm1@...ntu.com
Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure
Hi,
on 25 Nov 09 at 17:53, Krzysztof Halasa wrote:
> Jarod Wilson <jarod@...sonet.com> writes:
[...]
>> nimble. If we can come up with a shiny new way that raw IR can be
>> passed out through an input device, I'm pretty sure lirc userspace can
>> be adapted to handle that.
As Trent already pointed out, adding support for raw IR through an input
device would require a new interface too. You just put the label "input
device" on it. This does not make much sense for me.
> Lirc can already handle input layer. Since both ways require userspace
> changes,
I'm not sure what two ways you are talking about. With the patches posted
by Jarod, nothing has to be changed in userspace.
Everything works, no code needs to be written and tested, everybody is
happy.
We had exactly the same discussion around one year ago. I've seen no new
arguements in the current discussion and nobody came up with this shiny
new way of integrating LIRC into the input layer since last year. Maybe
it's about time to just accept that the LIRC interface is the way to go.
Can we finally get the patch integrated, please?
Christoph
--
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