On Fri, 20 Sep 2019 15:37:08 +0200, Rafał Miłecki wrote: > From: Rafał Miłecki <rafal@xxxxxxxxxx> > > Hardware or firmware instability may result in unusable wiphy. In such > cases usually a hardware reset is needed. To allow a full recovery > kernel has to indicate problem to the user space. > > This new nl80211 command lets user space known wiphy has crashed and has > been just recovered. When applicable it should result in supplicant or > authenticator reconfiguring all interfaces. > > Signed-off-by: Rafał Miłecki <rafal@xxxxxxxxxx> > --- > I'd like to use this new cfg80211_crash_report() in brcmfmac after a > successful recovery from a FullMAC firmware crash. > > Later on I'd like to modify hostapd to reconfigure wiphy using a > previously used setup. > > I'm OpenWrt developer & user and I got annoyed by my devices not auto > recovering after various failures. There are things I cannot fix (hw > failures or closed fw crashes) but I still expect my devices to get > back to operational state as soon as possible on their own. Perhaps a slightly larger point, but I think it should be raised - is there any chance for reusing debugging, reset and recovery work done in devlink originally for complex Ethernet devices? WiFi drivers have been dealing with more complex/FW heavy designs for a while so maybe you've grow your own interfaces, and maybe they necessarily need to be 802.11-centric, but I'm a little surprised that: linux $ git grep devlink -- drivers/net/wireless/ linux $ _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
