On Tuesday 27 November 2007 21:02:47 Larry Finger wrote: > Michael, > > I'm getting a little closer. The problem I discovered now is that b43_leds_init() was being called > before b43_rfkill_init(), which prevented registration of the "radio" LED. Now, the LED is flashed > on for about 1 second, then it goes off. Changing the switch does nothing. Ok, good catch. Is the switch properly polled and is the status change properly reported upstream? If yes, you might want to check (add printk to rfkill code) if the LED is properly triggered. > This version uses mutex_trylock() to see if the mutex is already locked. It should do until rfkill > is fixed. No it doesn't. This still introduces a race. I'm wondering who causes this deadlock. "registered" should be false if we are called back from rfkill_initialize, so it should return early before the lock. -- Greetings Michael. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
