I had a discussion with Matthew Garrett about handling of a wifi killswitch on a Dell laptop. Some (rfkill) code was removed from platform/dell-laptop. On my machine a bug now occurs which is caused by brcmsmac in the view of Matthew. So is this a bug, or do you have no killsitch handling, so far? Bug description: > physical switch is OFF > rfkill state is ON > => Laptop hangs on boot (maybe because a physical ascent device is > used by network subsystem) > > physical switch is OFF > rfkill state is OFF > => Activate interface in Gnome Connection Manager => System hang > > test setup: > Dell Vostro 3300 > Broadcom 4313 Wifi > Kernel 3.5.[0-2] & 3.6 > Fedora 17 What Matthew wrote to me: > > With the old dell-laptop code included everything was fine with > > brcmsmac. So either generic platform code does not handle the switch > > correct or there is no handling at all? > > brcmsmac is broken. I suspect it was happily claiming to be > unblocked, > but was ignored because dell-laptop claimed to be blocked. Full discussion thread: https://lkml.org/lkml/2012/8/23/234 -- 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