[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091208172543.GA14271@core.coreip.homeip.net>
Date: Tue, 8 Dec 2009 09:25:43 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Krzysztof Halasa <khc@...waw.pl>
Cc: Mauro Carvalho Chehab <mchehab@...hat.com>,
Jon Smirl <jonsmirl@...il.com>,
hermann pitton <hermann-pitton@...or.de>,
Christoph Bartelmus <lirc@...telmus.de>, awalls@...ix.net,
j@...nau.net, jarod@...hat.com, jarod@...sonet.com,
kraxel@...hat.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel
IR system?
On Tue, Dec 08, 2009 at 02:57:15PM +0100, Krzysztof Halasa wrote:
> Dmitry Torokhov <dmitry.torokhov@...il.com> writes:
>
> > Why woudl we want to do this? Quite often there is a need for "observer"
> > that maybe does not act on data but allows capturing it. Single-user
> > inetrfaces are PITA.
>
> Lircd can work as a multiplexer.
What this has to do with my statement? Did you mean retransmitter of sorts?
Also I may explicitely not want the data stream to be multiplexed...
> IMHO single-open lirc interface is ok,
> though we obviously need simultaneous operation of in-kernel decoders.
Why is the distinction?
--
Dmitry
--
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