On Wed, 2007-08-15 at 18:38 -0700, Jouni Malinen wrote: > I don't linke next_mode either, so if this is combined to a single > atomic operation, it would be quite a bit better way to do this. Yeah, we'll have that if somebody gets around to it. > I would assume that the quick workaround for this would have been to > change the configuration file to use 802.11g instead of the default > i802.11b.. Oh, it was :) But it wasn't obvious. > Anyway, the design used here does indeed assume that the > driver exports all supported mode/channel pairs and in case the hardware > card supports 802.11g, the driver would most likely claim support for > both 802.11b and 802.11g channels. > > Adding code for reverting back to 802.11g version would, in theory, be > fine for most cases, but it does have some issues.. If I remember > correctly, channel 14 may only be used with 802.11b mode in Japan, so > the list of 802.11b and 802.11g channels is not the same. In this > particular case, though, the workaround of using 802.11g list would not > cause a problem (the other direction would potentially have). Hmm. That seems like something to be integrated with the regulatory code rather than the driver. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
