On 03/31/2015 07:27 AM, Johannes Berg wrote: > On Wed, 2015-03-11 at 14:05 -0700, Ben Greear wrote: > >> I took a look at the hw-scan code a bit...I guess we might could do additional >> info calls to user-space as we iterate through the channels while scanning? >> >> A real driver would be causing the NIC to change channels at these junctures, >> either by directly setting registers or sending some message off to the >> target NIC's cpu, right? > > Well, depends. Our driver just asks the firmware to do the scan, and it > will do all the scheduling by itself, i.e. it'll go through the channels > at convenient times etc. I do not want to offload scanning in user-space, which is the equivalent of what your driver is doing as far as the kernel is concerned? If someone wants to do that in the future, then sure, they can implement such a thing. >> I would assume that off-channel work could do similar logic. > > Yeah. > >> Is that the sort of thing you had in mind? > > To be honest, I'm not really sure myself. It seems to really do this > you'd also need powersave handling (tell the AP you're going to sleep > when scanning) and potentially P2P-GO NoA handling (tell the clients > you're going to sleep). Yes, I have plans to do that sort of thing..but I have not looked into it properly yet. Either way, it seems a bit orthogonal to changing the channel..like first we send the PS packets, then change channel, etc. > The thing with hwsim right now is that it totally makes use of its > ability to be on as many channels at the same time as it wants, so it > doesn't have to worry about that, but if you want to actually have the > channel "changed" then we need to handle a lot more details. One step at a time I think...my patch should not break anything..userspace that doesn't care can simply ignore the new message. Thanks, Ben > > johannes > -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- 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
