linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: johannes@sipsolutions.net, linville@tuxdriver.com,
	nbd@openwrt.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v5] cfg80211: Add nl80211 antenna configuration
Date: Mon, 2 Aug 2010 13:13:54 +0900	[thread overview]
Message-ID: <201008021313.54850.br1@einfach.org> (raw)
In-Reply-To: <AANLkTi=ihY=pAmKaEp7Pga=DOxwASZqSxqmURbgnks-d@mail.gmail.com>

On Fri July 30 2010 00:04:49 Luis R. Rodriguez wrote:
> >> I don't want to do any work myself on drivers for this, can we have
> >> cfg80211/mac80211 do this for us?
> > 
> > is this not a separate issue from defining the API? you could have it do
> > this for you even now, with or without the antenna API, no?
> 
> It depends on the consumer and at what level we think the consumer
> should be doing whatever checks or changes it should. For starters I
> would expect at least a check for association within cfg80211 which
> disallows hw config changes. 

for ath5k at least, it's o.k. to change antenna configuration during 
association.

if 802.11n devices cannot change antenna setup during association, the driver 
could simply reject the configuration. but i can see that it can make sense to 
handle some of this in cfg80211 or mac80211. it should be possible to add that 
on top of my patches.

i think you are expecting to much. for now i just want to define an API which 
1) can be used right now and 2) is flexible enough to support 802.11n devices. 
as i don't work with 802.11n devices right now, please don't expect me to 
solve all 802.11n related antenna problems. as long as the API is flexible 
enough i think it can be added later as 802.11n devices are going to accept 
antenna configuration.

bruno

  reply	other threads:[~2010-08-02  4:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  3:58 [PATCH v5] cfg80211: Add nl80211 antenna configuration Bruno Randolf
2010-07-29  6:12 ` Luis R. Rodriguez
2010-07-29  7:48   ` Johannes Berg
2010-07-29  9:12   ` Bruno Randolf
2010-07-29 15:04     ` Luis R. Rodriguez
2010-08-02  4:13       ` Bruno Randolf [this message]
2010-08-02  5:37         ` Luis R. Rodriguez
2010-08-02  8:59           ` Felix Fietkau
2010-08-02  9:10             ` Luis R. Rodriguez
2010-08-02  9:17               ` Felix Fietkau
2010-08-02  9:23                 ` Luis R. Rodriguez
2010-08-02  9:32                   ` Felix Fietkau
2010-08-02  9:52                     ` Luis R. Rodriguez
2010-08-02 10:10                       ` Felix Fietkau
2010-08-02 10:18                         ` Luis R. Rodriguez
2010-08-02 10:47                           ` Felix Fietkau
2010-08-02 10:51                             ` Luis R. Rodriguez
2010-08-02 11:18                               ` Felix Fietkau
2010-08-02 17:45                                 ` Luis R. Rodriguez
2010-08-02 11:01                             ` Johannes Berg
2010-08-02 11:19                               ` Felix Fietkau

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=201008021313.54850.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=nbd@openwrt.org \
    /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).