linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	ath5k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath5k: add possible wiphy interface combinations
Date: Mon, 16 Apr 2012 09:02:04 -0700	[thread overview]
Message-ID: <4F8C427C.3020505@candelatech.com> (raw)
In-Reply-To: <1334590102-83386-1-git-send-email-nbd@openwrt.org>

On 04/16/2012 08:28 AM, Felix Fietkau wrote:
> Signed-off-by: Felix Fietkau<nbd@openwrt.org>
> ---
>   drivers/net/wireless/ath/ath5k/base.c |   16 ++++++++++++++++
>   1 files changed, 16 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath5k/base.c b/drivers/net/wireless/ath/ath5k/base.c
> index 3007bba..2e385f5 100644
> --- a/drivers/net/wireless/ath/ath5k/base.c
> +++ b/drivers/net/wireless/ath/ath5k/base.c
> @@ -2415,6 +2415,19 @@ ath5k_tx_complete_poll_work(struct work_struct *work)
>   * Initialization routines *
>   \*************************/
>
> +static const struct ieee80211_iface_limit if_limits[] = {
> +	{ .max = 256,	.types = BIT(NL80211_IFTYPE_STATION) },
> +	{ .max = 4,	.types = BIT(NL80211_IFTYPE_AP) |
> +				 BIT(NL80211_IFTYPE_MESH_POINT) },
> +};

The station max is just an arbitrary number or is 256 really
the max it can handle?  At least on ath9k, more are supported,
but I haven't tested ath5k lately....

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2012-04-16 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 15:28 [PATCH] ath5k: add possible wiphy interface combinations Felix Fietkau
2012-04-16 16:02 ` Ben Greear [this message]
2012-04-16 16:07   ` Felix Fietkau
2012-04-16 16:11     ` Ben Greear

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=4F8C427C.3020505@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).