From: Johannes Berg <johannes@sipsolutions.net>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net,
Abhijeet Kolekar <abhijeet.kolekar@intel.com>
Subject: Re: [PATCH] mac80211: Fix n-band association problem
Date: Thu, 17 Apr 2008 18:58:40 +0200 [thread overview]
Message-ID: <1208451520.4066.25.camel@johannes.berg> (raw)
In-Reply-To: <1208379724-13568-1-git-send-email-reinette.chatre@intel.com> (sfid-20080416_220312_598962_80DA4049)
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
On Wed, 2008-04-16 at 14:02 -0700, Reinette Chatre wrote:
> From: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
>
> There are two structures named wmm_info and wmm_param, they are used while
> parsing the beacon frame. (Check the function ieee802_11_parse_elems).
> Certain APs like D-link does not set the fifth bit in WMM IE.
> While sending the association request to n-only ap it checks for wmm_ie.
> If it is set then only ieee80211_ht_cap is sent during association request.
> So n-only association fails.
> And this patch fixes this problem by copying the wmm_info to wmm_ie,
> which enables the "wmm" flag in iee80211_send_assoc.
>
> Signed-off-by: Abhijeet Kolekar <abhijeet.kolekar@intel.com>
> Acked-by: Ron Rindjunsky <ron.rindjunsky@intel.com>
Ack, thanks for the update.
> ---
>
> This problem is also present in 2.6.25. This patch does apply to
> 2.6.25-rc9 after changing the filename to be patched to ieee80211_sta.c
Do we want this for -stable then?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-04-17 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 21:02 [PATCH] mac80211: Fix n-band association problem Reinette Chatre
2008-04-17 16:58 ` Johannes Berg [this message]
2008-04-17 17:05 ` Chatre, Reinette
2008-04-17 17:18 ` Johannes Berg
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=1208451520.4066.25.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=abhijeet.kolekar@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.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).