From: Felix Fietkau <nbd@openwrt.org>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: thomas@net.t-labs.tu-berlin.de, x-alina@gmx.net,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Add transmit power control support (TPC)
Date: Mon, 09 Jul 2012 21:43:37 +0200 [thread overview]
Message-ID: <4FFB3469.4000003@openwrt.org> (raw)
In-Reply-To: <4FFB2E78.9090402@gmail.com>
On 2012-07-09 9:18 PM, Xose Vazquez Perez wrote:
> Thomas Huehn wrote:
>
>> (6) restructure tx-path of all effected drivers
>> Restructure tx-path of all effected drivers to respect new TPC support in
>> mac80211. TPC support is added to mac80211 by restructuring of struct
>> ieee80211_tx_info. Therfore the tx-path of all effected drivers is modified
>> to receive struct sta from the stack and respect the new ieee80211_tx_info
>> struct. List of modified driver:
>
>> ath9k
>> ath5k
>> iwl3954
>> iwl4965
>> iwl-agn
>> mwl8k
>> carl9170
>> ath9k-htc
>> p54
>> rt2x00
>> rtl8180
>> rtl8087
>> hwsim
>> b43
>> b43legacy
>> brcmsmac
>> zd1211rw
>
> candidates:
>
> ath6kl
> brcmfmac
> iwmc3200wifi
> mwifiex
> rndis_wlan
No. (fullmac, thus unaffected by the change)
> libertas_tf
> rtlwifi
> wl1251
> wl12xx
Yes, those indeed look like they need to be added.
- Felix
next prev parent reply other threads:[~2012-07-09 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 19:18 [PATCH] mac80211: Add transmit power control support (TPC) Xose Vazquez Perez
2012-07-09 19:43 ` Felix Fietkau [this message]
2012-07-09 20:26 ` Xose Vazquez Perez
2012-07-09 21:22 ` Thomas Huehn
-- strict thread matches above, loose matches on Subject: below --
2012-07-08 17:02 Thomas Huehn
2012-07-09 9:37 ` Johannes Berg
2012-07-09 9:55 ` thomas
2012-07-09 10:00 ` Johannes Berg
2012-07-09 10:13 ` Johannes Berg
2012-07-09 10:43 ` Thomas Huehn
2012-07-16 20:47 ` Hin-Tak Leung
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=4FFB3469.4000003@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@net.t-labs.tu-berlin.de \
--cc=x-alina@gmx.net \
--cc=xose.vazquez@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).