From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] [PATCH 0/1] fix for 2.6.35
Date: Tue, 10 Aug 2010 10:04:32 -0700 [thread overview]
Message-ID: <1281459872.6027.6.camel@wwguy-ubuntu> (raw)
In-Reply-To: <AANLkTinJtJGQCgpWCu5t+EF7bEvXR3cQG7oHuagrjd1a@mail.gmail.com>
Hi Luis,
On Tue, 2010-08-10 at 09:51 -0700, Luis R. Rodriguez wrote:
> On Mon, Aug 9, 2010 at 10:57 AM, Wey-Yi Guy <wey-yi.w.guy@intel.com> wrote:
> > This patch required for 2.6.35 to fix 5GHz association problem. Without this,
> > iwlagn device will have issue connecting to 11a AP
> >
> > Johannes Berg (1):
> > iwlagn: fix rts cts protection
>
> This patch has an awesome commit log entry and describes issues with
> the current RTS mechanism and improvements made on the patch for
> different scenarios but in no way talks about issues with association
> with 5 GHz APs. Can you clarify in the commit log how it cures issues
> with 5 GHz, if that is indeed an intended fix for it?
>
Johannes might be able to add more, the original attempt of this patch
is to prevent un-necessary protection for non-data frames which we
introduced few rc ago. while we fix this, but we also found out this
patch also address the issue we have for 5GHz unable to associate to AP.
Thanks
Wey
next prev parent reply other threads:[~2010-08-10 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 17:57 [PATCH 0/1] fix for 2.6.35 Wey-Yi Guy
2010-08-09 17:57 ` [PATCH 1/1] iwlagn: fix rts cts protection Wey-Yi Guy
2010-08-10 16:51 ` [ipw3945-devel] [PATCH 0/1] fix for 2.6.35 Luis R. Rodriguez
2010-08-10 17:04 ` Guy, Wey-Yi [this message]
2010-08-10 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=1281459872.6027.6.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@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).