From: Pavel Roskin <proski@gnu.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Tomas Winkler <tomasw@gmail.com>,
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:50:03 -0400 [thread overview]
Message-ID: <1211482203.18709.9.camel@dv> (raw)
In-Reply-To: <1211481249.28022.15.camel@localhost.localdomain>
On Thu, 2008-05-22 at 14:34 -0400, Dan Williams wrote:
> But what's the best fix to the supplicant? It could just parse A-band
> channels and where the numbers overlap, assume B/G band. Or, it could
> be patched to prefer FREQ+frequency over FREQ+channel if it received
> both. That's probably the best solution.
I checked the wpa_supplicant sources and I see that all it needs is the
frequency. All that needs to be done is not to allow channels
(everything below, say, 10000) overwrite existing frequency data.
That's the second approach.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-05-22 18:50 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 [this message]
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
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=1211482203.18709.9.camel@dv \
--to=proski@gnu.org \
--cc=dcbw@redhat.com \
--cc=egrumbach@gmail.com \
--cc=johannes@sipsolutions.net \
--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