[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060728134408.GE29217@suse.cz>
Date: Fri, 28 Jul 2006 15:44:08 +0200
From: Vojtech Pavlik <vojtech@...e.cz>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Shem Multinymous <multinymous@...il.com>,
"Brown, Len" <len.brown@...el.com>, Pavel Machek <pavel@...e.cz>,
Matthew Garrett <mjg59@...f.ucam.org>,
kernel list <linux-kernel@...r.kernel.org>,
linux-thinkpad@...ux-thinkpad.org, linux-acpi@...r.kernel.org
Subject: Re: Generic battery interface
On Fri, Jul 28, 2006 at 08:25:35AM -0400, Dmitry Torokhov wrote:
> On 7/28/06, Vojtech Pavlik <vojtech@...e.cz> wrote:
> >On Fri, Jul 28, 2006 at 03:27:00AM +0300, Shem Multinymous wrote:
> >>
> >> "Generic interface for accelerometers (AMS, HDAPS, ...)" on LKML, a
> >> few weeks ago, about moving accelerator-based hard disk parking from
> >> sysfs polling to the the input infrastructure. One unresolved issue
> >> was how to find which input device happens to be the relevant
> >> accelerometer.
> >
> >The current well known methods are:
> >
> > 1) udev/hotplug. It can create device nodes and symlinks based on
> > the
> > capabilities and IDs of an input device.
> > 1a) HAL. It has all the info from hotplug as well.
> > 2) open them all and do the capability checks / IDs yourself.
> > 3) (obsolete, deprecated) parse /proc/bus/input/devices, which
> > lists all the input devices
> >
>
> 4) sysfs - all capabilities, IDs, etc for input devices exported there as
> well.
Oh, of course. I don't know how I could forget sysfs here - I had it in
mind when I started writing the list ...
--
Vojtech Pavlik
Director SuSE Labs
-
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