Util-Linux package development
 help / color / mirror / Atom feed
From: Paul Fox <pgf@laptop.org>
To: Daniel Drake <dsd@laptop.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Karel Zak <kzak@redhat.com>,
	util-linux@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] evstate: new utility for querying evdev key/switch/event state
Date: Tue, 12 Jul 2011 16:07:00 -0400	[thread overview]
Message-ID: <15489.1310501220@foxharp.boston.ma.us> (raw)
In-Reply-To: <CAGq3pz4ueyiTg1usRwangBJfuPwYPoOC0k83ygKs2RikfOQyGw@mail.gmail.com> (sfid-20110711_124927_157078_A3E8F7E6)

daniel wrote:
 > On 11 July 2011 17:39, Dmitry Torokhov <dmitry.torokhov@gmail.com> 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.)

paul
=---------------------
 paul fox, pgf@laptop.org

  reply	other threads:[~2011-07-12 20:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 13:20 [PATCH] evstate: new utility for querying evdev key/switch/event state Daniel Drake
2011-07-11 12:18 ` Karel Zak
2011-07-11 13:12   ` Daniel Drake
2011-07-11 13:14     ` Daniel Drake
2011-07-11 16:39   ` Dmitry Torokhov
2011-07-11 16:48     ` Daniel Drake
2011-07-12 20:07       ` Paul Fox [this message]
2011-07-12 20:35         ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15489.1310501220@foxharp.boston.ma.us \
    --to=pgf@laptop.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dsd@laptop.org \
    --cc=kay.sievers@vrfy.org \
    --cc=kzak@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox