public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fox <pgf@laptop.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Zhang Rui <rui.zhang@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"Brown, Len" <lenb@kernel.org>
Subject: Re: a question about lid input device
Date: Wed, 07 Jul 2010 13:08:18 -0400	[thread overview]
Message-ID: <18986.1278522498@foxharp.boston.ma.us> (raw)
In-Reply-To: <20100707170125.GB25178@core.coreip.homeip.net> (sfid-20100707_130135_399456_EE95C65A)

dmitry wrote:
 > On Wed, Jul 07, 2010 at 12:51:04PM -0400, Paul Fox wrote:
 > > dmitry wrote:
 > >  > On Wed, Jul 07, 2010 at 11:14:20AM -0400, Paul Fox wrote:
 ...
 > >  > > i understand that it's not fully general, but for the case of
 > >  > > the lid:  is /proc/acpi/button/lid/LID/state going away?
 > >  > 
 > >  > Yes, according to feature-removal.txt ACPI procfs interface shoudl have
 > >  > been gone back in 2008.
 > > 
 > > thanks.  i understand that adding sysfs entries for all the bells
 > > and whistles on modern input devices might seem prohibitive.  on
 > > the other hand, there are some basic interfaces that are very
 > > usefully accessed from the shell.  i guess either way the
 > > information is available, but having to rely on a utility package
 > > for intermediate access always introduces new packaging
 > > dependencies, release skew issues, etc, etc.
 > > 
 > 
 > I am not wasting kernel memory to export full state of an arbitrary
 > input device via sysfs just so someone out there might avoid writing or
 > installig a utility. The interface was there for many years and is quite
 > stable, I do not understand what release skew issues you are talking
 > about.

if, for example, the utility package available in a distro lags
behind the kernel.

but please consider my comments above as more of a lament than a
complaint.  i understand your design decision -- it will make
your life easier, at the expense of making mine somewhat more
difficult.  :-)

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

  reply	other threads:[~2010-07-07 17:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13  6:53 a question about lid input device Zhang Rui
2010-06-14  2:01 ` Henrique de Moraes Holschuh
2010-06-22  1:56   ` Len Brown
2010-07-04  8:35     ` Dmitry Torokhov
2010-07-05  1:09       ` Zhang Rui
2010-07-05  1:28         ` Dmitry Torokhov
2010-07-05  1:47           ` Zhang Rui
2010-07-05 19:49             ` Henrique de Moraes Holschuh
2010-07-05 20:04               ` Paul Fox
2010-07-05 20:27               ` Dmitry Torokhov
2010-07-07  3:08                 ` Zhang Rui
2010-07-07  5:36                   ` Dmitry Torokhov
2010-07-07 15:14   ` Paul Fox
2010-07-07 16:25     ` Dmitry Torokhov
2010-07-07 16:51       ` Paul Fox
2010-07-07 17:01         ` Dmitry Torokhov
2010-07-07 17:08           ` Paul Fox [this message]
2010-07-07 17:19             ` Dmitry Torokhov
2010-09-29  1:12       ` Len Brown

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=18986.1278522498@foxharp.boston.ma.us \
    --to=pgf@laptop.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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