wifi: Update help/notes for forcing regulatory domain
With recent changes the regulatory domain is handled via the hostap rather than by passing and going through the driver and hostap doesn't have any option for forcing the regulatory domain, so, add a note to reflect that this is implementation dependent to cover both hostap as well other offloaded implementations. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>
This commit is contained in:
parent
6b11e91ce0
commit
9762c32115
2 changed files with 5 additions and 2 deletions
|
@ -874,7 +874,9 @@ struct wifi_reg_chan_info {
|
|||
struct wifi_reg_domain {
|
||||
/** Regulatory domain operation */
|
||||
enum wifi_mgmt_op oper;
|
||||
/** Ignore all other regulatory hints over this one */
|
||||
/** Ignore all other regulatory hints over this one, the behavior is
|
||||
* implementation specific.
|
||||
*/
|
||||
bool force;
|
||||
/** Country code: ISO/IEC 3166-1 alpha-2 */
|
||||
uint8_t country_code[WIFI_COUNTRY_CODE_LEN];
|
||||
|
|
|
@ -3433,7 +3433,8 @@ SHELL_SUBCMD_ADD((wifi), reg_domain, &wifi_commands,
|
|||
"Set or Get Wi-Fi regulatory domain\n"
|
||||
"[ISO/IEC 3166-1 alpha2]: Regulatory domain\n"
|
||||
"[-f]: Force to use this regulatory hint over any other regulatory hints\n"
|
||||
"Note: This may cause regulatory compliance issues, use it at your own risk.\n",
|
||||
"Note1: The behavior of this command is dependent on the Wi-Fi driver/chipset implementation\n"
|
||||
"Note2: This may cause regulatory compliance issues, use it at your own risk.\n",
|
||||
cmd_wifi_reg_domain,
|
||||
1, 2);
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue