I've observed an undesirable change in behaviour of rt2x00 as a result of Johannes Berg's patch 3d4803379613c763f5a7863e8249b63d190af5e6 (remove all prism2 ioctls). It used to consistently default to 802.11g mode on g capable hardware. Because that patch removed the lines - /* Use next_mode as the mode preference to - * resolve non-unique channel numbers. */ - if (set && mode->mode != local->next_mode) - continue; in ieee80211_set_channel it now defaults to 11b unless I change the code that calls ieee80211_register_hwmode. (I realise that the next_mode test is no longer "right"). This is because ieee80211_set_channel will now prefer to select whichever was the last mode for which the driver called ieee80211_register_hwmode whereas the previous behaviour preferred the first registered mode. It seems as though if there was a way to avoid calling Iieee80211_set_channel then the setting of oper_hw_mode in ieee80211_register_hwmode would still prefer the first registered mode. Is it intended that the order of calling ieee80211_register_hwmode should determine which mode should be preferred when multiple modes exist on the same channel or is there either already or planned a better option for driver writers? If calling order should determine preference should it be first or last registered? Adam Baker - 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
