Antonio Quartulli <antonio@xxxxxxxxxxxxx> writes: > On Wed, Jun 05, 2013 at 02:57:07AM -0700, Kalle Valo wrote: >> Antonio Quartulli <ordex@xxxxxxxxxxxxx> writes: >> >> > I'm looking at ath6kl_mgmt_tx() in ath6kl/cfg80211.c and I've seen that the >> > currently "configured" frequency can be obtained by reading the >> > ath6kl_vif->ch_hint field. >> > >> > But, is this correct? >> >> I did a quick look. To me using ch_hint looks correct. >> >> > I couldn't see any real relation between the ch_hint field and the >> > real frequency (probably because a lot of logic is hidden to the >> > driver). I could only understand that the ch_hint field stores the >> > frequency passed as parameter during the connection, but I have found >> > no guarantee that this is the really used one. >> >> Can you be more specific, please? >> >> To me it looks that ch_hint is used both with ath6kl_wmi_reconnect_cmd() >> and ath6kl_wmi_connect_cmd() commands, which both are used to connect to >> a network. I don't see any other variables used for specifying the >> frequency to the firmware. But I could just be blind... > > I agree with your analysis. My doubt came from the fact that I don't know what > the firmware does and I was wondering whether it could ignore the channel passed > as argument on connect for some reason. It might do that, I'm not involved with the firmware development. > Actually the doubt was raised due to the variable name "ch_HINT". Yeah, the name is really misleading. But that's still legacy from the pre-cleanup driver, so I wouldn't worry about that too much. > But you are the ath6k expert :-) Therefore I guess this can work. It should but you never know :) But when modifying that code, please add a check to make sure that channel 0 is not used by accident. -- Kalle Valo -- 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
