From: Johannes Berg <johannes@sipsolutions.net>
To: Bruno Randolf <br1@einfach.org>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 1/3] cfg80211: Add nl80211 antenna configuration
Date: Tue, 08 Jun 2010 11:05:02 +0200 [thread overview]
Message-ID: <1275987902.3706.107.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <201006081010.13314.br1@einfach.org>
On Tue, 2010-06-08 at 10:10 +0900, Bruno Randolf wrote:
> i don't particularly care about where the antenna information is printed
> exactly, so anything will be fine with me.
>
> but when i look at the wiphy info, it shows mostly capability information,
> like the list of supported frequencies, list of bitrates, supported interface
> modes, supported commands. the only exception is coverage class, which is the
> only runtime configuration as far as i can see. therefore i thought it doesnt
> fit there well.
>
> maybe another command for getting runtime configuration like channel(s), fixed
> bitrates, essid, bssid, RTS/CTS, fraqmentation, txpower, power management,
> antenna settings, etc... would make sense? allthough in this list antenna is
> probably the only one which is per phy and not per interface...
Right so there isn't much runtime stuff in the list now. I don't see
anything inherently bad in adding more though, since userspace can
selectively look at the attributes, and it's not like it's a huge amount
of data?
johannes
prev parent reply other threads:[~2010-06-08 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 6:58 [PATCH v3 1/3] cfg80211: Add nl80211 antenna configuration Bruno Randolf
2010-06-07 6:59 ` [PATCH v3 2/3] mac80211: Add " Bruno Randolf
2010-06-07 6:59 ` [PATCH v3 3/3] ath5k: Add support for " Bruno Randolf
2010-06-07 9:03 ` [PATCH v3 1/3] cfg80211: Add nl80211 " Johannes Berg
2010-06-08 1:19 ` Bruno Randolf
2010-06-08 7:27 ` Johannes Berg
2010-06-07 9:05 ` Johannes Berg
2010-06-08 1:10 ` Bruno Randolf
2010-06-08 9:05 ` 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=1275987902.3706.107.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=br1@einfach.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.