From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, sgruszka@redhat.com
Subject: Re: [RFC] iwl4965: report A-MPDU status
Date: Sat, 19 Jan 2013 23:15:54 +0100 [thread overview]
Message-ID: <1358633754.5472.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <201301190030.11771.chunkeey@googlemail.com> (sfid-20130119_004037_956066_34B3CA0C)
On Sat, 2013-01-19 at 00:30 +0100, Christian Lamparter wrote:
> 1. This patch [including commit msg] is a copy of:
> commit 12bf6f45d17038589e0eaa8adeb7ee8169c0e4de
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Thu Jul 5 13:05:08 2012 +0200
> iwlwifi: report A-MPDU status
:-)
> 2. RX_RES_PHY_FLAGS_ANTENNA_MSK
> I had the chance to test this with a real 4965.
> As far as I can tell, the hardware has just 3
> antenna connectors. But I have seen frames, which
> apparently have been received on 4 antennas?!
>
> Note: iwlwifi had this problem as well. It was
> fixed by:
> commit 362b0563b28506d534a82d9c6cd5fdf58783fda6
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Fri Aug 24 11:13:17 2012 +0200
> iwlwifi: fix antenna bitmask
> I suppose 4965 also uses the 4th bit as the AMPDU
> indicator. It would be very helpful if someone
> could confirm this assumption. [Otherwise the
> whole AMPDU status feature patch has little use].
I can't easily verify this this right now, but I think it's a safe bet
since no iwlegacy/iwlwifi device exists that supports 4 antennas, and
the definition in question has always been the same for all hardware. I
just didn't fix it for 4965 since it was split off to iwlegacy already.
johannes
prev parent reply other threads:[~2013-01-19 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 23:30 [RFC] iwl4965: report A-MPDU status Christian Lamparter
2013-01-19 22:15 ` Johannes Berg [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=1358633754.5472.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.