On 09/10/2015 12:22 AM, Johannes Berg wrote:
On Wed, 2015-09-09 at 12:49 -0400, Bob Copeland wrote:
On Wed, Sep 09, 2015 at 12:10:38PM +0300, Kalle Valo wrote:
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;
OK, this happens when mesh is configured out (we mask off the mesh
interface_modes internally but not the types). Sent an updated
version with appropriate ifdefs added.
Yeah this is an unfortunate quirk in the APIs ... I think adding the
ifdefs to the driver is the best thing to do.
johannes
Can we configure mesh point with hostapd or can we use mesh point
without neither wpa_supplicant nor hostapd?
Currently I'm trying to bring up mesh point, but whenever I run hostpad
after creating mesh point (iw phy0 interface add mesh type mp), hostapd
change the interface mode to managed.
_______________________________________________
ath10k mailing list
ath...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
Thanks,
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
