From: Dan Williams <dcbw@redhat.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Vincent C Jones <v.jones@networkingunlimited.com>,
linux-wireless@vger.kernel.org,
Emmanuel Grumbach <egrumbach@gmail.com>
Subject: Re: iwl4965 - wpa_supplicant can't see 5Ghz frequencies - 2.6.26-rc1 kernel
Date: Thu, 22 May 2008 14:22:59 -0400 [thread overview]
Message-ID: <1211480579.28022.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1ba2fa240805220953u746d3429q50faa1885104cadb@mail.gmail.com>
On Thu, 2008-05-22 at 19:53 +0300, Tomas Winkler wrote:
> On Mon, May 12, 2008 at 9:37 PM, Vincent C Jones
> <v.jones@networkingunlimited.com> wrote:
> >
> > On Mon, 2008-05-12 at 19:50 +0300, Tomas Winkler wrote:
> >
> >> Meanwhile we've reproduced the wpa_supplicant issue...
> >>
> >
> > That is great news. Let me know when it is time to test again...
>
> Please try this one. I've just pasted that in so it's might be
> white-space-wise broken
>
> diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
> index 7877d3b..5996e3d 100644
> --- a/net/mac80211/mlme.c
> +++ b/net/mac80211/mlme.c
> @@ -4080,17 +4080,18 @@ ieee80211_sta_scan_result(struct net_device *dev,
> IW_EV_UINT_LEN);
> }
>
> +
> memset(&iwe, 0, sizeof(iwe));
> iwe.cmd = SIOCGIWFREQ;
> - iwe.u.freq.m = bss->freq;
> - iwe.u.freq.e = 6;
> + iwe.u.freq.m = ieee80211_frequency_to_channel(bss->freq);
> + iwe.u.freq.e = 0;
> current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe,
> IW_EV_FREQ_LEN);
>
> memset(&iwe, 0, sizeof(iwe));
> iwe.cmd = SIOCGIWFREQ;
> - iwe.u.freq.m = ieee80211_frequency_to_channel(bss->freq);
> - iwe.u.freq.e = 0;
> + iwe.u.freq.m = bss->freq;
> + iwe.u.freq.e = 6;
> current_ev = iwe_stream_add_event(current_ev, end_buf, &iwe,
> IW_EV_FREQ_LEN);
Wait a minute; what's mac80211 sending _two_ FREQ events for? That's
not right.
Dan
next prev parent reply other threads:[~2008-05-22 18:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 16:57 iwl4965 - wpa_supplicant can't see 5Ghz frequencies - 2.6.26-rc1 kernel Vincent C Jones
2008-05-09 21:23 ` Tomas Winkler
2008-05-09 23:41 ` Vincent C Jones
2008-05-10 0:12 ` Tomas Winkler
2008-05-10 2:36 ` Vincent C Jones
2008-05-10 14:39 ` Vincent C Jones
2008-05-10 15:46 ` Vincent C Jones
2008-05-10 18:56 ` Tomas Winkler
2008-05-10 21:48 ` Vincent C Jones
2008-05-10 22:06 ` Tomas Winkler
2008-05-11 2:49 ` Vincent C Jones
2008-05-12 16:50 ` Tomas Winkler
2008-05-12 18:37 ` Vincent C Jones
2008-05-22 16:53 ` Tomas Winkler
2008-05-22 17:42 ` Dann Church
2008-05-22 17:54 ` Tomas Winkler
2008-05-24 11:03 ` Dann Church
2008-05-22 17:56 ` Johannes Berg
2008-05-22 17:58 ` Tomas Winkler
2008-05-22 18:34 ` Dan Williams
2008-05-22 18:50 ` Pavel Roskin
2008-05-22 19:18 ` Dan Williams
2008-05-22 19:21 ` Johannes Berg
2008-05-22 18:51 ` Tomas Winkler
2008-05-22 19:12 ` Johannes Berg
2008-05-22 19:30 ` Dan Williams
2008-05-22 19:34 ` Johannes Berg
2008-05-22 20:56 ` Tomas Winkler
2008-05-22 21:09 ` Johannes Berg
2008-05-22 22:07 ` Dan Williams
2008-05-22 18:22 ` Dan Williams [this message]
2008-05-22 19:16 ` Johannes Berg
2008-05-22 22:33 ` Vincent C Jones
2008-05-22 22:50 ` Tomas Winkler
2008-05-22 23:28 ` Vincent C Jones
2008-05-10 17:06 ` Tomas Winkler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1211480579.28022.5.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=v.jones@networkingunlimited.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox