On Fri, 2009-06-05 at 23:38 +0200, Michael Buesch wrote: > Hell, just return a freaking error from b43_rfkill_poll(), if the interface > is down. If rfkill can't handle that, it should probably be taught to handle it. > Especially as there can be other errors as well, like memory allocation failures. Be my guest. You'll notice eventually that it's not really easy or possible to do. I've explained the currently broken scenario already. And even if you introduce the 'unknown' state, you still end up having to poll the bit when userspace tries to turn on the device... doesn't help much. Larry, thanks for your patch, I'll modify it to turn off the core again after checking the rfkill bit tomorrow. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
