From: Kalle Valo <kalle.valo@nokia.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Tomas Winkler <tomasw@gmail.com>, 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: Mon, 12 May 2008 21:04:48 +0300 [thread overview]
Message-ID: <87ve1j9z5r.fsf@nokia.com> (raw)
In-Reply-To: <1210328819.3547.90.camel@johannes.berg> (ext Johannes Berg's message of "Fri\, 09 May 2008 12\:26\:59 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
>> 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.
>
> Speaking of which, what about the Nokia AP bug that cx3110x works
> around? :)
Hah hah, I had forgotten that one altogether :) I don't think we want
to take that route, that is enabling workarounds for APs based on
BSSID. That's going to be a maintainance nightmare in the long run, at
least in my opinion.
We should have one A032 in our office somewhere, I'll try to find it
and see how b43 works with it.
(For others wondering what we are talking about: Nokia 770/N800/N810
products enable long slot time when associating to Nokia A032 AP to
workaround a bug in the AP.)
--
Kalle Valo
prev parent reply other threads:[~2008-05-12 18:05 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
2008-05-09 10:26 ` Johannes Berg
2008-05-12 18:04 ` Kalle Valo [this message]
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=87ve1j9z5r.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).