From: Kalle Valo <kvalo@codeaurora.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: Luka Perkov <luka.perkov@sartura.hr>, ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: enable advertising support for channels 32, 68 and 98
Date: Tue, 09 Jun 2020 14:57:39 +0300 [thread overview]
Message-ID: <87y2owmoy4.fsf@codeaurora.org> (raw)
In-Reply-To: <20200327093147.189390-1-robert.marko@sartura.hr> (Robert Marko's message of "Fri, 27 Mar 2020 10:31:47 +0100")
Robert Marko <robert.marko@sartura.hr> writes:
> Enable advertising support for 5G channels: 32, 68 and 96.
> These channels are legal and available for use in ETSI countries.
> So lets advertise these and they will be available in accordance with the regulatory domain used.
>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> Cc: Luka Perkov <luka.perkov@sartura.hr>
What's the use case for this? I was told that the IEEE standard does not
define these channels, that's why I'm asking for more information.
On what hardware and firmware did you test this? It might be that not
all hardware or firmware support this.
There was a concern if this slows down scanning due to more channels
being scanned, but I haven't analysed that yet. Did you measure that?
Also please CC linux-wireless on ath10k patches. Otherwise patchwork
won't see them and it won't be on my radar:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/submittingpatches
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-06-09 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 9:31 [PATCH] ath10k: enable advertising support for channels 32, 68 and 98 Robert Marko
2020-06-04 12:07 ` Robert Marko
2020-06-09 11:57 ` Kalle Valo [this message]
2020-06-10 12:18 ` Robert Marko
2020-06-11 11:29 ` Markus Theil
2020-06-11 12:05 ` Markus Theil
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=87y2owmoy4.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=luka.perkov@sartura.hr \
--cc=robert.marko@sartura.hr \
/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.