On Mon, Sep 29, 2008 at 12:25:23PM +0200, Johannes Berg wrote: > > Isn't ath5k reporting quite a large set of channels that would never > > really be used? 26 channels on 2.4 GHz and 194(huh!) on 5 GHz.. First > > workaround could be to just limit those to somewhat more common set of > > channels. > > Well, this is what the hw supports I guess, most channels will actually > reported to userspace with the DISABLED flag set. Well.. It reports channels like 2732 MHz or 6100 MHz and 5 GHz center frequencies for every possible multiple of 5 MHz. If someone is really using those properly, they are on a licensed band and this types of lists are not really needed for normal users. Whether the hardware really supports them or well, more exactly, whether all selected components can handle these frequencies and whether the radios have been calibrated for all of these areas is another question. > > > > There is also a bug in hostapd which waits for ACK forever when this error occur > > > > in i802_get_hw_feature_data(). For some reason, I do not seem to be able to reproduce this. Both iw and hostapd were able to fetch the data using the current wireless-testing tree.. > I recently rewrote the handling in iw completely to make it easier to > follow, will post an equivalent patch for hostapd in a minute. Anyway, cleanup for nl send/recv processing is certainly welcome. I've never fully understood the steps that are used there and what to do if anything went wrong.. -- 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
