From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: dmitry.torokhov@gmail.com From: Dmitry Torokhov To: Paul Fox Subject: Re: [PATCH] evstate: new utility for querying evdev key/switch/event state Date: Tue, 12 Jul 2011 13:35:41 -0700 Cc: Daniel Drake , Karel Zak , util-linux@vger.kernel.org, Kay Sievers , linux-input@vger.kernel.org References: <20110709132046.90A119D401C@zog.reactivated.net> <15489.1310501220@foxharp.boston.ma.us> In-Reply-To: <15489.1310501220@foxharp.boston.ma.us> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Message-Id: <201107121335.41556.dmitry.torokhov@gmail.com> List-ID: On Tuesday, July 12, 2011 01:07:00 PM Paul Fox wrote: > daniel wrote: > > On 11 July 2011 17:39, Dmitry Torokhov wrote: > > > Now I'd say that this utility probably better fit into linuxconsole > > > project with the rest of input-related utilities... > > > > http://sourceforge.net/projects/linuxconsole/ ? > > > > This must have been what you were referring to before. Yes, this > > looks like a more appropriate home. I'll take it in that direction. > > i disagree. the contents of that package seems to be mostly for > testing and legacy support. access to the state of input switches in > a generic way seems far more generally useful than that. > > i would rather not see the sysfs state variable go away in the first > place -- it's too convenient to use, and inexpensive to implement -- > needing an ioctl for this seems like a step backwards. but barring > that, relegating the evstate functionality to linuxconsole seems wrong. > (for instance, i don't think the OLPC laptop distros have a need for > any of the other utilities in linuxconsole.) You can package only what you need from it, no need to package everything. -- Dmitry