Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties
From: Kalle Valo <hidden>
Date: 2017-01-04 14:32:44
Also in:
linux-wireless
Possibly related (same subject, not in this thread)
- 2017-01-04 · Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties · Arend Van Spriel <hidden>
- 2017-01-04 · Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties · Rafał Miłecki <hidden>
- 2017-01-03 · Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties · Rafał Miłecki <hidden>
- 2017-01-03 · Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties · Rob Herring <hidden>
- 2016-12-28 · Re: [PATCH 1/2] dt-bindings: document common IEEE 802.11 frequency properties · Rafał Miłecki <hidden>
Rafał Miłecki [off-list ref] writes:
On 3 January 2017 at 20:55, Rob Herring [off-list ref] wrote:quoted
On Wed, Dec 28, 2016 at 04:59:54PM +0100, Rafał Miłecki wrote:quoted
From: Rafał Miłecki <redacted> This new file should be used for properties handled at higher level and so usable with all drivers.Why is this needed? Where would this data normally come from?Vendors limit choice of channels at their web user interface level. I want to do better and report proper channels directly at kernel level instead of masking them in every possible configuration tool.
Why do vendors limit the channels? Is it because of a hardware limitation (antenna does not support, or not calibrated, for a certain band etc) or something else? -- Kalle Valo