All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Daniel Drake <drake@endlessm.com>
Cc: franky.lin@broadcom.com, hante.meuleman@broadcom.com,
	chi-hsien.lin@cypress.com, wright.feng@cypress.com,
	linux-wireless@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com,
	brcm80211-dev-list@cypress.com,
	Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: brcmfmac signal/interference issues
Date: Fri, 23 Feb 2018 10:54:33 +0100	[thread overview]
Message-ID: <5A8FE4D9.80608@broadcom.com> (raw)
In-Reply-To: <CAD8Lp44Y-sNqm8_5=1pvBy-3zvVVQSCQ+Qye-2xP8vGmkvrjng@mail.gmail.com>

On 2/23/2018 9:26 AM, Daniel Drake wrote:
> Hi,
>
> On Wed, Feb 21, 2018 at 12:39 PM, Daniel Drake <drake@endlessm.com> wrote:
>> Thanks for looking into this. Here is the brcmfmac43455-sdio.txt file
>> we are using:
>> https://gist.github.com/dsd/d7ee3caa6dfd77f0bcd16cf272b20298
>> This is identical to the 4345r6nvram.txt file from windows.
>
> I checked Windows again and it seems to be using a firmware file
> 4345r6rtecdc.bin alongside this nvram data.
> This firmware is different from the one in linux-firmware. I've
> uploaded it here:
> https://drive.google.com/open?id=1MUsiaoozslJb8SCYOR-FNbJFuD-h4PY_
>
> I was hoping to try this on Linux to see if it makes any difference to
> the issue seen here.
> However, with thisi firmware in place, I can't connect to the network
> at all. It associates, wpa_supplicant never sees the first WPA2 key
> message sent from the AP - even though wireshark on a separate monitor
> shows that the key message was sent, and that the STA acked it.
>
> I turned off WPA2 to make it an open network instead, and now I am
> unable to complete the DHCP conversation. According to the monitor
> station, the STA succesfully transmits DHCPDISCOVER and the AP
> responds with DHCPOFFER. The offer is acked, but dhclient never sees
> it, and eventually times out.
>
> Any ideas why this firmware may not be working at all on linux?

Yup. Windows firmware talks NDIS. If you run 'strings 4345r6rtecdc.bin | 
tail -1' you can see the firmware build target and it likely has 'ndis' 
in it.

Now are you using BT as well on this device? Another suggestion I got is 
to disable transmit beamforming which brcmfmac enables by default. Not 
sure if this device supports it, but could you try the patch below.

Regards,
Arend

diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c 
b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
index 9be0b05..512ea57 100644
--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.c
@@ -363,9 +363,6 @@ int brcmf_c_preinit_dcmds(struct brcmf_if *ifp)
                 goto done;
         }

-       /* Enable tx beamforming, errors can be ignored (not supported) */
-       (void)brcmf_fil_iovar_int_set(ifp, "txbf", 1);
-
         /* do bus specific preinit here */
         err = brcmf_bus_preinit(ifp->drvr->bus_if);
  done:

  reply	other threads:[~2018-02-23  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21  8:14 brcmfmac signal/interference issues Daniel Drake
2018-02-21  9:07 ` Arend van Spriel
2018-02-21  9:39   ` Daniel Drake
2018-02-21 11:04     ` Arend van Spriel
2018-02-23  8:26     ` Daniel Drake
2018-02-23  9:54       ` Arend van Spriel [this message]
2018-02-23 13:49         ` Daniel Drake
2018-03-08 10:47           ` Arend van Spriel
2018-03-08 15:54             ` Steve deRosier
2018-03-09  9:35               ` Arend van Spriel
2018-03-28 18:03               ` Daniel Drake
2018-03-28 18:43             ` Daniel Drake
2018-04-03  7:28               ` Arend van Spriel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A8FE4D9.80608@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211-dev-list@cypress.com \
    --cc=chi-hsien.lin@cypress.com \
    --cc=drake@endlessm.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@endlessm.com \
    --cc=wright.feng@cypress.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.