that correct the announced interface
combinations. I am currently on vacation as my family expanded with a
baby girl.
Regards,
Arend
The error I see is:
brcmfmac: _brcmf_set_mac_address: Setting cur_etheraddr failed, -52
with -52 meaning BCME_IE_NOTFOUND.
--
To unsubscribe from this list: send
On 9 July 2015 at 20:08, Arend van Spriel ar...@broadcom.com wrote:
On 07/09/2015 09:07 AM, Rafał Miłecki wrote:
Hey guys, I'm afraid I hit another brcmfmac bug.
First of all, I implemented a trivial workaround for the previous bug
reported in the:
brcmfmac: one faulty iw interface add
. That obviously doesn't work.
The error I see is:
brcmfmac: _brcmf_set_mac_address: Setting cur_etheraddr failed, -52
with -52 meaning BCME_IE_NOTFOUND.
I managed to find/guess what exactly BCM43602 firmware rejects. It
doesn't like 2 MAC addresses that differ by the locally administrated
bit only
and finally having two networks (SSIDs)
using the same MAC. That obviously doesn't work.
The error I see is:
brcmfmac: _brcmf_set_mac_address: Setting cur_etheraddr failed, -52
with -52 meaning BCME_IE_NOTFOUND.
I managed to find/guess what exactly BCM43602 firmware rejects. It
doesn't like 2
