[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091128013443.GL6936@core.coreip.homeip.net>
Date: Fri, 27 Nov 2009 17:34:44 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Jon Smirl <jonsmirl@...il.com>
Cc: Ferenc Wagner <wferi@...f.hu>,
Christoph Bartelmus <lirc@...telmus.de>, awalls@...ix.net,
christoph@...telmus.de, j@...nau.net, jarod@...hat.com,
jarod@...sonet.com, khc@...waw.pl, 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 Fri, Nov 27, 2009 at 02:21:13PM -0500, Jon Smirl wrote:
> On Fri, Nov 27, 2009 at 2:03 PM, Ferenc Wagner <wferi@...f.hu> wrote:
> > Admittedly, I don't know why /dev/mouse is evil, maybe I'd understand if
>
> /dev/mouse is evil because it is possible to read partial mouse
> messages. evdev fixes things so that you only get complete messages.
>
For me the main evil of /dev/mouse (and other multuiplexing interfaces)
is that it is impossible to remove one of the streams from the
multiplexed stream without affecting other users. And so are born
various "grab" schemes where we declare one application _the
application_ and let it "grab" the device.. which breaks when there are
other applications also interested in the same data stream.
--
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