From: Dan Williams <dcbw@redhat.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
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 18:07:41 -0400 [thread overview]
Message-ID: <1211494061.10742.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1ba2fa240805221356g681c49e4r9cd7f8c80f57801f@mail.gmail.com>
On Thu, 2008-05-22 at 23:56 +0300, Tomas Winkler wrote:
> On Thu, May 22, 2008 at 10:34 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> >
> >> > Fun. How about it we just make wpa supplicant ignore FREQ/channel
> >> > completely if it uses FREQ/frequency anyway?
> >>
> >> Can't because some drivers send channel and not frequency. Yeah, we
> >> could fix all the drivers, but that doesn't help people running latest
> >> supplicant on older kernels.
> >
> > Oh, good point. I guess the patch you posted is the only sane thing to
> > do then, and require that drivers that work in the 5 GHz band send
> > frequency (because there channel numbers need not be unique due to
> > 802.11j's channelisation offset)
> >
>
> Fix in the mac should go in as well in so it will work with older
> supplicants and it doesn't really hurt.
Yup. Both parts (mac80211 FREQ re-order, and supplicant patch) should
be applied.
Dan
next prev parent reply other threads:[~2008-05-22 22:07 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 [this message]
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=1211494061.10742.3.camel@localhost.localdomain \
--to=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