From: Kalle Valo <kalle.valo@nokia.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Helmut Schaa" <hschaa@suse.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
"John Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH/RFC v2] mac80211: fix association with some APs
Date: Fri, 09 May 2008 10:56:34 +0300 [thread overview]
Message-ID: <87ej8bykp9.fsf@nokia.com> (raw)
In-Reply-To: <1ba2fa240805081445p4fb5e47cvf2743a868c7887ae@mail.gmail.com> (ext Tomas Winkler's message of "Fri\, 9 May 2008 00\:45\:57 +0300")
Tomas Winkler <tomasw@gmail.com> writes:
> On Thu, May 8, 2008 at 2:36 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
>> On Thu, 2008-05-08 at 13:34 +0200, Helmut Schaa wrote:
>> > Some APs refuse association if the supported rates contained in the
>> > association request do not match its own supported rates. This patch
>> > introduces a new function which builds the intersection between the AP's
>> > supported rates and the client's supported rates to work around such
>> > problems. The same approach is already used in ipw2200 for example.
>> >
>> > Signed-off-by: Helmut Schaa <hschaa@suse.de>
>>
>> Thanks. Looks ok to me.
>
> Are we sure there is no firmware with the fix for this AP?
Most probably this isn't the only AP which has a similar bug, so it's
better to add a workaround anyway. Let's just hope that it doesn't
create any regressions.
--
Kalle Valo
next prev parent reply other threads:[~2008-05-09 7:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 8:30 [PATCH/RFC] mac80211: fix association with some APs Helmut Schaa
2008-05-08 8:57 ` Johannes Berg
2008-05-08 11:34 ` [PATCH/RFC v2] " Helmut Schaa
2008-05-08 11:36 ` Johannes Berg
2008-05-08 21:45 ` Tomas Winkler
2008-05-08 21:51 ` Johannes Berg
2008-05-08 22:10 ` Tomas Winkler
2008-05-09 7:56 ` Kalle Valo [this message]
2008-05-09 10:26 ` Johannes Berg
2008-05-12 18:04 ` Kalle Valo
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=87ej8bykp9.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=hschaa@suse.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.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;
as well as URLs for NNTP newsgroup(s).