From: Ben Greear <greearb@candelatech.com>
To: 정승현 <hyun11man@naver.com>, ath10k@lists.infradead.org
Subject: Re: ath10k channel in tx process
Date: Mon, 29 Jan 2018 08:22:16 -0800 [thread overview]
Message-ID: <5A6F4A38.1080809@candelatech.com> (raw)
In-Reply-To: <637bbe18904038b339d2565e6364eb70@cweb27.nm.nhnsystem.com>
On 01/29/2018 04:05 AM, 정승현 wrote:
> Hi all,
>
> I am trying to figure out how ath10k (operating in AP mode) handles the channel on which an AP sends packets to one of its associated stations. I have found a few functions including ath10k_sta_state set channel information for each station, but I couldn't find out which function(s) utilize the information while tx processing. Is there any function for channel selection while processing tx?
The channel is set up as part of bringing up the vdev, I think. You do not have per-peer
control over normal sending...but the driver can do off-channel tx, which allows you to
temporarily change channels and send frames.
>
> BTW, Does ath10k support broadcast and multicast? or always convert them into unicast? If it supports broadcast and multicast, does it always use 20MHz?
A sniffer would answer this question for you...at least most firmware are probably sending multicast. Some may convert to
unicast. Possibly the driver/stack could do similar logic to convert to unicast if it cared.
Thanks,
Ben
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2018-01-29 16:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <636e3ee2f7c034676d717c7b2f9aa4fc@cweb07.nm.nhnsystem.com>
2018-01-29 12:05 ` ath10k channel in tx process 정승현
2018-01-29 16:22 ` Ben Greear [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=5A6F4A38.1080809@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=hyun11man@naver.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.