On Mon, May 12, 2014 at 03:26:23PM +0200, Arend van Spriel wrote: > I was wondering how to configure the bandwidth of the operating > channel in P2P-GO scenario. In nl80211.c I do see the use of > .set_ap_chanwidth() callback. Reading the spec it seems the > operating channel is exchanged during GO negotiation, but I do not > see any reference about the bandwidth. It does exchange the > operating class and I found some info in p2p_supplicant.c (see > below). I am just not sure how this is configured to the driver, ie. > what nl80211 commands will be used. In theory, operating class could be used to negotiate channel bandwidth during GO Negotiation. In practice, though, most implementations do not do this. Instead, the device that becomes the GO can just decide to enable 40 MHz (or 80/80+80/160 MHz for VHT) on its own regardless of which operating class was used. This should still be done in a way that the primary channel ends up being where indicating during GO Negotiation to allow the P2P Client to find the GO more easily. -- Jouni Malinen PGP id EFC895FA -- 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
