- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Cypress IOT team.
[Info]
- FMAC: 2020-01-15
https://community.cypress.com/docs/DOC-19000
- wpa_supplicant: version 2.9
[Background]
THE current FMAC driver does not call "wiphy_apply_custom_regulatory" when cfg80211 up. The "wiphy_apply_custom_regulatory" means applying a custom driver regulatory to the kernel.
Because of it, regulatory info does not match between chip side① and kernel side② like below.
====
wl channels
1 2 3 4 5 6 7 8 9 10 11 ... ①
./wpa_cli
> get_capability channels
Mode
====
To call "wiphy_apply_custom_regulatory" when cfg80211 up, I modified FMAC source code "cfg80211.c". The patch is attached.
Then I can see an expected behavior.
[Need Help]
Please review the attached patch.
Thanks,
Yoshinori
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thank you for the patch. It work with the current setup. The regulatory info is taken from the clm_blob that goes with the firmware. We currently dont use the information from the kernel regulatory information
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thank you for the patch. It work with the current setup. The regulatory info is taken from the clm_blob that goes with the firmware. We currently dont use the information from the kernel regulatory information
Regards