| commit | 256faf7cfa938ac2750c09305ba489e75462896b | [log] [tgz] |
|---|---|---|
| author | Nicolas Norvez <norvez@chromium.org> | Mon Nov 02 00:56:28 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 28 02:27:44 2021 |
| tree | 7ec1dc0f87834f16fea28d93129bac98193ce9db | |
| parent | 659a3e2a6024907d08da035ce40d67ea36285d50 [diff] |
Reland "CHROMIUM: iwlwifi: only support GeoSAR v0 tables" This is a reland of 8cd0ea5195e72b943d092a43a21d90bb4084674a Original change's description: > CHROMIUM: iwlwifi: only support GeoSAR v0 tables > > Some existing GeoSAR tables incorrectly set the version field to 1 > instead of 0 to mean that the contents of the table are invalid and > should be ignored. > However, recent versions of iwlwifi have started handling version 1 as > valid, resulting in incorrect GeoSAR tables being applied on those > devices. > Until we have audited and fixed those broken GeoSAR tables, keep > supporting only v0 tables. > > BUG=b:172034758 > TEST=load a v1 GeoSAR table that sets TX power to 0 on a device, observe > that the driver rejects the table and does not send the broken SAR table > to the firmware. > > Change-Id: I029d2a2226f62d6201a3eda1bdf9745fa2e9f0ae > Signed-off-by: Nicolas Norvez <norvez@chromium.org> > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/2513538 > Reviewed-by: Brian Norris <briannorris@chromium.org> Bug: b:172034758 Change-Id: I0e570729366ad05c16b814466a05974a165d1c02 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/2649493 Tested-by: Nicolas Norvez <norvez@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> Commit-Queue: Nicolas Norvez <norvez@chromium.org> (cherry picked from commit 229d34ae33cb6167190c3c4f92535bfda0b96d19) Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/2653557 Reviewed-by: Nicolas Norvez <norvez@chromium.org>