|
From: Alex D. <ale...@gm...> - 2007-05-21 13:38:59
|
On 5/21/07, Henrique de Moraes Holschuh <hm...@hm...> wrote: > On Mon, 21 May 2007, Richard Hughes wrote: > > Has there been any work on implementing rfkill for thinkpad_acpi? If > > there is nobody working on this I am offering to add support into > > thinkpad_acpi this week. > > Yes, I have been talking to the rfkill people, but we had some disagreements > on how to best to it. I let it rest for a week or so to think better about > some issues they raised, and also in order not to waste too much bandwidth > from either side of the issue. > > Basically, I want a "fetch data from the hardware to know what state it is > in for real" interface. They want a "find a way to make sure the hardware > is doing what we told it to do" interface. > > I might even find out that we are better off not using rfkill in > thinkpad-acpi itself, and letting the bluetooth and wwan drivers process it. > We shall see. The thinkpad ACPI interface does a lot more than just > radio-kill, it actually kills power to the *devices* themselves, AFAIK > (removes them from the USB bus, causing hotunplug events). Anyone with a > bluetooth and WWAN device, please speak up. On my t41p, fn-f5 "unplugs" the bluetooth chip from the USB bus. For the mini-pci atheros wifi, fn-f5 seems to turn off the radio only. Alex |
