AR6003 5.2GHz AP on channel 38

[Rostyslav Khudolii]

Hi Jouni,

Thank you for your reply.

I don't really have to use them, but their presence in the driver
implies that they can be used since they're populated via cfg80211
subsystem to the userspace (wpa_supplicant, iw).

So, I guess, the best solution is to just remove them from ath6kl?

On 7 March 2017 at 17:07, Malinen, Jouni <jouni at qca.qualcomm.com> wrote:
> On Tue, Mar 07, 2017 at 03:58:37PM +0100, Rostyslav Khudolii wrote:
>> As far as I know, AR6003 (according to the specs) supports both
>> 802.11a and 802.11an modes and the difference between those to, when
>> it comes to operating frequencies, is actually a set of 38/42/46
>> channels, which are supported as primary by 802.11a and are not by
>> 802.11n.
>
> Why would you use channels 38, 42, and 46 (and 34 which would also be in
> this set)? Those are the old 5 GHz channels that were initially defined
> for Japan, but are not used anymore. There is no difference here for
> 802.11a between 802.11n (well, apart from 802.11n being new enough that
> it may have actually been published only after the channel definitions
> in Japan had already happened).
>
>> So, my question is: would it be feasible to just remove those channels
>> from the supported list and forget about 802.11a like it's done in
>> ath10?
>
> The only reason for listing channels 34, 38, 42, and 46 is for old
> device compatibility in products sold in Japan. That said, those
> channels have been removed from new products long time ago, so it might
> make sense to remove them from ath6kl as well. If someone has a valid
> use case for them, a custom patch could be used instead. In any case,
> support for such channels would depend on the full network stack both
> above and below the driver supporting them and that's unlikely to be the
> case nowadays.
>
>> If no - how do I enable 802.11a then?
>
> By using currently define channels (36, 40, 44, ..).
>
> --
> Jouni Malinen                                            PGP id EFC895FA