No, the flag CONFIG_CFG80211_INTERNAL_REGDB does not help and it should not. The problem is that cfg80211 will stuck in situation when cfg80211 is initialized before user space. One way to get cfg80211 out of this state is to run crda once right after user space is up and running. But again is this intentional? Or it is more like a workaround? 2013/9/9 Kalle Valo <kvalo@xxxxxxxxxx>: > Eugene Krasnikov <k.eugene.e@xxxxxxxxx> writes: > >> There is a problem with regulatory part of cfg80211 when cfg80211 is >> built-in the kernel. On regulatory init cfg80211 will try to notify >> user space about changing current domain to world regulatory but at >> that time user space is not up and running yet and uevent message will >> be lost. So what will happen is that cfg80211 will wait for the >> response from user space and all requests to set current regulatory >> will be dropped with the following error: “Pending regulatory request, >> waiting for it to be processed...”. > > Does CONFIG_CFG80211_INTERNAL_REGDB help? > > -- > Kalle Valo -- Best regards, Eugene -- 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
