Re: [PATCH 1/3] dt-bindings: net: wireless: add flag marvell,ignore-regulatory-hint
Krzysztof Kozlowski <[email protected]>
| Newsgroups | org.kernel.vger.stable,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-wireless |
|---|---|
| Message-ID | <20260817-hairy-serval-of-refinement-49039a@quoll> |
On Fri, Aug 14, 2026 at 03:50:23PM +0300, Georgi Valkov wrote: > WRT3200ACM and WRT32x routers always report a fixed US regulatory domain > from the mwifiex ROM, which conflicts with the platform regulatory > configuration on units sold outside the US market. For example: > - phy0 mwlwifi 5 GHz, hard-coded region 98 EU mapped to FR > - phy1 mwlwifi 2.4 GHz, hard-coded region 98 EU mapped to FR > - phy2 mwifiex 2.4 and 5 GHz, hard-coded region US v1 as reply to v3 in big thread. How tools can parse that? Does b4 diff work? b4 diff '[email protected]' > > When the system boots, it detects a conflict between the user selected > region and the radios, e.g. BG FR US, and applies extreme restrictions, > preventing use of 5 GHz and DFS channels. This also affects phy0. > > Add a device-tree flag, which allows affected platforms to ignore > an incorrect regulatory hint from ROM, so userspace can set the > correct platform regulatory domain. > > [1] https://github.com/kaloz/mwlwifi/issues/173#issuecomment-307879699 > [2] https://github.com/openwrt/openwrt/issues/9956 > > Tested-on: WRT3200ACM, OpenWrt Not a valid tag, drop. And you cannot even do that, otherwise explain me how did your device execute THIS (exactly THIS) code? > Cc: [email protected] Drop, what is the bug being fixed here? Anyway, property looks like SW choice. You must describe hardware instead. Best regards, Krzysztof