From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Bruno Randolf <br1@einfach.org>,
linville@tuxdriver.com, mcgrof@gmail.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v7 1/3] cfg80211: Add nl80211 antenna configuration
Date: Wed, 10 Nov 2010 16:59:38 +0100 [thread overview]
Message-ID: <4CDAC16A.2050300@openwrt.org> (raw)
In-Reply-To: <1289404367.3748.0.camel@jlt3.sipsolutions.net>
On 2010-11-10 4:52 PM, Johannes Berg wrote:
> On Wed, 2010-11-10 at 12:50 +0900, Bruno Randolf wrote:
>
>> 802.11n devices should enable or disable chains, based on which antennas are
>> present (If all antennas belonging to a particular chain are disabled, the
>> entire chain should be disabled). HT capabilities (like STBC, TX Beamforming,
>> Antenna selection) should be calculated based on the available chains after
>> applying the antenna masks. Should a 802.11n device have diversity antennas
>> attached to one of their chains, diversity can be enabled or disabled based on
>> the antenna information.
>
> I'm not entirely convinced that this is a good idea. Nor that, even if
> 11n devices were to implement it, they should all implementing their own
> code to update the HT capabilities. However, I suppose that nothing
> forces them to implement it, and when somebody does I can still complain
> when they put everything into the driver.
Drivers already need to calculate their HT capabilities based on the
number of chains.
If chains get masked out based on the antenna mask settings, the driver
code would most of the time only need minor refactoring for updating the
settings which wouldn't necessarily result in any new code duplication
at all.
- Felix
next prev parent reply other threads:[~2010-11-10 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 3:50 [PATCH v7 1/3] cfg80211: Add nl80211 antenna configuration Bruno Randolf
2010-11-10 3:50 ` [PATCH v7 2/3] mac80211: Add " Bruno Randolf
2010-11-10 3:51 ` [PATCH v7 3/3] ath5k: Add support for " Bruno Randolf
2010-11-10 15:52 ` [PATCH v7 1/3] cfg80211: Add nl80211 " Johannes Berg
2010-11-10 15:59 ` Felix Fietkau [this message]
2010-11-10 16:24 ` Johannes Berg
2010-11-19 18:45 ` Johannes Berg
2010-11-19 18:49 ` Johannes Berg
2010-11-22 9:53 ` Bruno Randolf
2010-12-06 3:47 ` Bruno Randolf
2010-11-22 2:33 ` Bruno Randolf
2010-11-22 15:31 ` Johannes Berg
2010-11-24 1:45 ` Bruno Randolf
2010-12-01 6:43 ` Johannes Berg
2010-12-01 6:47 ` Bruno Randolf
2010-12-01 6:54 ` Johannes Berg
2010-12-01 8:48 ` Johannes Berg
2010-12-02 7:23 ` Bruno Randolf
2010-12-02 7:28 ` Johannes Berg
2010-12-02 20:37 ` Luis R. Rodriguez
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=4CDAC16A.2050300@openwrt.org \
--to=nbd@openwrt.org \
--cc=br1@einfach.org \
--cc=johannes@sipsolutions.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 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.