f808c43ad9
iwlwifi can return early from probe (in FreeBSD attach) while a separate thread is still grinding loading the firmware and setting things up. For us this means that kldload succeeded but we may not have a physical wireless interface (com) yet but the rc framework might already try to configure a vap on one. Wait until we get a firmware completion event from the other thread (on success or error) and block returning. That way we can ensure that the "hw" (or com in net80211 terms) is there when we return from attach matching the expected FreeBSD driver behaviour. Reported by: J.R. Oldroyd (jr opal.com) Reported by: probably inderectly showing as other problem Tested by: J.R. Oldroyd (jr opal.com) Sponsored by: The FreeBSD Foundation MFC after: 3 days |
||
|---|---|---|
| .. | ||
| acpica | ||
| ath/ath_hal/ar9300 | ||
| ice | ||
| imx | ||
| ipw | ||
| iwi | ||
| iwlwifi | ||
| iwlwififw | ||
| iwm | ||
| iwn | ||
| liquidio | ||
| mwl | ||
| nvidia | ||
| otus | ||
| qat | ||
| qat_c2xxx | ||
| ral | ||
| rsu | ||
| rtw88 | ||
| rtw88fw | ||
| rtw89 | ||
| rtw89fw | ||
| rtwn | ||
| run | ||
| uath | ||
| wpi | ||