Skip to content
This repository has been archived by the owner on Sep 7, 2020. It is now read-only.

[TASK][Channel scan] use AP Radio Basic Capabilities TLV to validate channel pool #686

Closed
4 tasks done
kantera800 opened this issue Jan 16, 2020 · 2 comments
Closed
4 tasks done
Assignees
Labels
enhancement New feature or request

Comments

@kantera800
Copy link
Collaborator

kantera800 commented Jan 16, 2020

currently channel pool validated by static table supported_channels_array[] of channels in db::set_dcs_channel_pool()

This is incorrect since radio setup could vary with different country configuration.

We need permanent and generic prplMesh solution:

poc PR - do not merge #941

@arnout
Copy link
Collaborator

arnout commented Feb 18, 2020

create new structure in node.h std::vector<beerocks_message::sWifiChannel> phy_supported_channels
save GET_HW_FEATURES report during in slave_join to DB.

This is exactly what ap_wlan_hal->read_supported_channels() does, no? So what exactly needs to be done here?

@kantera800
Copy link
Collaborator Author

create new structure in node.h std::vector<beerocks_message::sWifiChannel> phy_supported_channels
save GET_HW_FEATURES report during in slave_join to DB.

This is exactly what ap_wlan_hal->read_supported_channels() does, no? So what exactly needs to be done here?

in case we are currently on a static channel and we want to scan , read_supported_channels() returns just this channel.
also , i heard that read_supported_channels() is not going to be used soon.
we need to store in the db latest channel list that fw supports for the dcs feature.

@kantera800 kantera800 changed the title [TASK][Channel scan] start using GET_HW_FEATURES for channel scan pool validation in db [TASK][Channel scan] use AP Radio Basic Capabilities TLV to validate channel pool Mar 31, 2020
@itayx itayx closed this as completed May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants