Hi Andrea, > Unfortunately it seems it does the same as mine.. Ok ... fair enough. > If this is not the case (no one knowns/tells) IMHO the two choice are: > - do what we said: parse beacons to extract channel information (and > let monitor mode stay as it is) Probably the best course of action for now. I'd make this conditional on receiving probe response/beacon, there should be helper functions for most of this. Since the chip is 2.4 GHz only you also don't have any problems with band selection stuff. > - do more investigation trying to fix also monitor mode issue. That could be done as a follow-up, I guess. > I could do some work on this (including opening the dongle to see if I > can put HW probes on the RF chip, to see on with frequency the FW > tunes it when scan commands are sent). > > Also AFAIK there is a new firmware in the off-tree Atmel driver, that > AFAIK also support WPA. > If this turns out to be true, then I'm tempted to rework the driver > for using it (hoping the the scan command works better on it). > > FYI : > Honestly I'm unsure if it's worth to do these last things: Whatever you want to do :-) johannes -- 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
