On Thu, Mar 15, 2012 at 10:11:49AM +0100, Johannes Berg wrote: > On Thu, 2012-03-15 at 14:32 +0530, Vasanthakumar Thiagarajan wrote: > > On Thu, Mar 15, 2012 at 09:58:27AM +0100, Johannes Berg wrote: > > > On Thu, 2012-03-15 at 14:27 +0530, Vasanthakumar Thiagarajan wrote: > > > > On Thu, Mar 15, 2012 at 09:51:28AM +0100, Johannes Berg wrote: > > > > > On Thu, 2012-03-15 at 14:12 +0530, Vasanthakumar Thiagarajan wrote: > > > > > > On Tue, Mar 13, 2012 at 04:06:03PM +0100, Johannes Berg wrote: > > > > > > > From: Johannes Berg <johannes.berg@xxxxxxxxx> > > > > > > > > > > > > > > My grand plan to allow drivers to gradually move over > > > > > > > to advertising virtual interface combinations and only > > > > > > > enforce with drivers that do want it enforced doesn't > > > > > > > seem to be working out, only Christian ever added the > > > > > > > advertising (to carl9170), nobody else did. > > > > > > > > > > > > > > Begin enforcing combinations in cfg80211 so that users > > > > > > > can rely on the information reported about a device. > > > > > > > > > > > > This breaks ath6kl AP mode and P2P, is it expected that the driver > > > > > > needs to register the combination (?) even it supports a single > > > > > > interface? > > > > > > > > > > Kalle tells me that ath6kl does support multiple virtual interfaces, but > > > > > if it didn't then it wouldn't have to register combinations. > > > > > > > > > > I suspect you're using > > > > > driver_param=use_p2p_group_interface=1 > > > > > in wpa_supplicant? > > > > > > > > Actually, I verified only AP mode, since it affects any sort of change interface, > > > > I mentioned P2P as well. AP is expected to work without any issue right?. > > > > > > As long as you don't try to add the AP interface as the second one... > > > > Right, I'm trying on a single interface. > > Hmm, ok, looking at the code again it seems there's a bug ... let me try > to fix it. V2 fixes this, thanks!. Vasanth -- 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
