On Fri, Sep 26, 2008 at 03:14:48PM +0100, Alan Jenkins wrote: > Matthew Garrett wrote: > > No, it's to use allow the OS to control whatever mechanism the platform > > provides for making the radio stop transmitting. The fact that this is, > > uh, "interestingly" implemented on the Eee doesn't alter that. > > So rfkill should be allowed to mean "entire PCI device goes away, > network interface will vanish" - just so long as it comes back correctly > when re-enabled :-). Sure, if that's how the platform implements it. This is how almost every bluetooth rfkill interface works, so applications should be able to cope. > > We should just sort out the hotplug code... > > > > Ok. I have a little knowledge, I'll see if I can be dangerous. My real > question was, is it safe to merge your rfkill support before this is > sorted out? I don't see why not. It works on various versions of the eee, and unless anything actually pokes it people can carry on using their bizarro userspace scripts. I'm working with the PCI guys on handling the hotplug case sanely. It may be possible to special case this in eeepc-laptop, though I'd prefer a more generic solution. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
