[ltp] rfkill in 2.6.27

[Henrique de Moraes Holschuh]

On Wed, 06 Aug 2008, Tino Keitel wrote:
> On Wed, Aug 06, 2008 at 09:43:42 -0300, Henrique de Moraes Holschuh wrote:
> > On Wed, 06 Aug 2008, Tino Keitel wrote:
> > > On Wed, Aug 06, 2008 at 00:05:22 +0200, Yves-Alexis Perez wrote:
> > > > due to brightness keys testing, I'm currently waving between 2.6.26 and
> > > > 2.6.27 (git). I noticed now the bluetooth LED is alway on when booting
> > > > (even when I blacklist hci_usb), and I now from reading thinkpad-acpi
> > > > documentation that /proc/acpi/ibm/bluetooth is deprecated and the sysfs
> > > > interface too.
> > > 
> > > I also noticed this.
> > 
> > rfkill will take its place.  But deprecated in thinkpad-acpi doesn't mean I
> > rip it off without warning.  It does mean you are not allowed to complain
> > when I finally rip it off, because you WERE warned it would be removed.
> > 
> > Expect the thinkpad-acpi-specific sysfs interface to stay around for a while
> > yet (one year or so, at least).  Procfs will go when /proc/acpi goes, and I
> > don't know when that will happen.
> > 
> > Look at Documentation/rfkill.txt if you want to know what's the new
> > interface like.
> 
> I looked over it to see what's the recommended way to get the current
> status and status changes in userspace. However, I'm too stupid and
> didn't get the point. Any hints what type of software and what type of
> communication between kernel and userspace is indended for rfkill? HAL,
> dbus, ACPI, input-device, something else?

You have only sysfs for now.  I think 2.6.27 will have uevents too.  It
eventually get into HAL, and from there, DBUS.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh