diff options
author | Daniel González Cabanelas <dgcbueu@gmail.com> | 2021-02-05 19:59:54 +0100 |
---|---|---|
committer | Álvaro Fernández Rojas <noltari@gmail.com> | 2021-02-07 19:08:08 +0100 |
commit | cf5e5204d976be00618f809b90c9c2156657903a (patch) | |
tree | 78c0e67cf28802b573b02730d021990992d2f94d /package/libs/wolfssl/patches | |
parent | 4465b44fc1a93ef4f480d22b405caae980f1b6f5 (diff) | |
download | upstream-cf5e5204d976be00618f809b90c9c2156657903a.tar.gz upstream-cf5e5204d976be00618f809b90c9c2156657903a.tar.bz2 upstream-cf5e5204d976be00618f809b90c9c2156657903a.zip |
bcm63xx: sprom: override the PCI device ID
The PCI device ID detected by the wifi drivers on devices using a fallback
SPROM is wrong. Currently the chipnum is used for this parameter.
Most SSB based Broadcom wifi chips are 2.4 and 5GHz capable. But on
devices without a physical SPROM, the only one way to detect if the device
suports both bands or only the 5GHz band, is by reading the device ID from
the fallback SPROM.
In some devices, this may lead to a non working wifi on a 5GHz-only card,
or in the best case a working 2.4GHz-only in a dual band wifi card.
The offset for the deviceid in SSB SPROMs is 0x0008, whereas in BCMA is
0x0060. This is true for any SPROM version.
Override the PCI device ID with the one defined at the fallback SPROM, to
detect the correct wifi card model and allow using the 5GHz band if
supported.
The patch has been tested with the following wifi radios:
BCM43222: b43: both 2.4/5GHz working
brcm-wl: both 2.4/5GHz working
BCM43225: b43: 2.4GHz, working
brcmsmac: working
brcm-wl: it lacks support
BCM43217: b43: 2.4GHz, working
brcmsmac: it lacks support
brcm-wl: it lacks support
Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Backported from a0e0e621ca
Diffstat (limited to 'package/libs/wolfssl/patches')
0 files changed, 0 insertions, 0 deletions