On Wed, 15 Mar 2006 09:40:52 -0800, Jouni Malinen wrote: > The same issue showed up with our low-level driver. How was the > low-level driver supposed to get this information with this change?
>From struct ieee80211_if_conf in add_interface callback. > d80211 part is likely fine, since it has the interface type available > like you mentioned, but I don't think that this is available to > low-level drivers(?). In other words, keeping this "int mode" in struct > ieee80211_conf may be useful even if we change d80211 to do something > else internally. If you have two interfaces running, one of STA type and of AP type, what should be the value of such "global mode" variable? It makes more sense to have per-interface mode and let driver decide what should be the mode it tells to the hardware. > Which driver did you use to test these changes? I have now successfully > tested both client and AP modes with bcm43xx_d80211 and Devicescape > driver for Atheros cards prior to applying these 13 changes. I would > like to verify that the new changes work properly before they are > applied into the wireless-2.6 tree. I can change our code easily, but I > would rather not touch bcm43xx_d80211 code to avoid any problems in > keeping the reverse engineered implementation clean as far as use of > proprietary information is concerned. Unfortunately, I'm not able to test AP mode as it's not supported by any available driver yet. For STA mode I use bcm43xx drivers. Thanks, -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
