Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> writes: > Bob Copeland <me@xxxxxxxxxxxxxxx> writes: > >> Add support for mesh to ath10k. We simply use an AP virtual interface >> in the firmware in order to enable beaconing without TSF adoption, and >> use the raw (802.11) transmit mode. >> >> Due to firmware limitations, the firmware must operate in raw >> (non-native 802.11) mode. As this is configured at firmware init time, >> a new "rawmode" modparam is added, and mesh interfaces are available >> only if rawmode=true. The firmware must advertise support for rawmode >> (tested successfully with firmware 10.2.4.70-2). >> >> When loaded with rawmode=1, ath10k can operate an open mesh STA via >> something like the following: >> >> ip link set wlan0 down >> iw dev wlan0 set type mp >> ip link set wlan0 up >> iw dev wlan0 set freq 5745 80 5775 >> iw dev wlan0 mesh join mesh-vht >> >> Signed-off-by: Bob Copeland <me@xxxxxxxxxxxxxxx> > > I did a quick smoke test and saw the splat below. It's this warning from > cfg80211: > > /* > * Don't advertise an unsupported type > * in a combination. > */ > if (WARN_ON((wiphy->interface_modes & types) != types)) > return -EINVAL; Forgot to mention that this was with 10.2.4.70.6-2 (which has the raw feature bit set, will push it soon) but rawmode modparam not set. And I had applied your patches on top of ath.git master branch (commit d89281c7d6bb9). -- Kalle Valo -- 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
