From: Joe Perches <joe@perches.com>
To: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Cc: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org,
ath6kl-devel@qualcomm.com
Subject: Re: [PATCH 2/2] ath6kl: Configure htcap in fw based on the channel type in AP mode
Date: Fri, 06 Apr 2012 07:54:26 -0700 [thread overview]
Message-ID: <1333724066.8565.6.camel@joe2Laptop> (raw)
In-Reply-To: <1333721235-16025-2-git-send-email-vthiagar@qca.qualcomm.com>
On Fri, 2012-04-06 at 19:37 +0530, Vasanthakumar Thiagarajan wrote:
> This patch disables HT in start_ap if the type of the channel on
> which the AP mode is going to be operating is non-HT. HT is enabled
> with default ht cap setting if the operating channel is going to be
> 11n.
[]
> diff --git a/drivers/net/wireless/ath/ath6kl/core.h b/drivers/net/wireless/ath/ath6kl/core.h
[]
> @@ -477,6 +477,12 @@ struct ath6kl_mc_filter {
> char hw_addr[ATH6KL_MCAST_FILTER_MAC_ADDR_SIZE];
> };
>
> +struct ath6kl_htcap {
> + bool ht_enable;
> + unsigned short cap_info;
> + u8 ampdu_factor;
> +};
Probably better to rearrange this as:
struct ath6kl_htcap {
unsigned short cap_info;
u8 ampdu_factor;
bool ht_enable;
};
next prev parent reply other threads:[~2012-04-06 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 14:07 [PATCH 1/2] ath6kl: Don't advertise HT40 support in 2.4 Ghz Vasanthakumar Thiagarajan
2012-04-06 14:07 ` [PATCH 2/2] ath6kl: Configure htcap in fw based on the channel type in AP mode Vasanthakumar Thiagarajan
2012-04-06 14:54 ` Joe Perches [this message]
2012-04-06 15:10 ` Vasanthakumar Thiagarajan
2012-04-06 17:41 ` Pedersen, Thomas
2012-04-07 12:55 ` Vasanthakumar Thiagarajan
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=1333724066.8565.6.camel@joe2Laptop \
--to=joe@perches.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vthiagar@qca.qualcomm.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).