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: Thu, 8 Mar 2018 11:47:05 +0100 [thread overview]
Message-ID: <5AA114A9.8050801@broadcom.com> (raw)
In-Reply-To: <CAD8Lp44Q0=jS0gqnt1mMfjRe6sTx3Z7n9=iGvk3VFGK2549V7g@mail.gmail.com>
On 2/23/2018 2:49 PM, Daniel Drake wrote:
> On Fri, Feb 23, 2018 at 12:54 PM, Arend van Spriel
> <arend.vanspriel@broadcom.com> wrote:
>> 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.
Hi Daniel,
Bit late response. Sorry.
> 43455c0-roml/sdio-ag-ndis-vista-pktfilter-d0c-pno-aoe-p2p-dhdoid-ndoe-gtkoe-mfp-proptxstatus-dmatxrc-keepalive-ap-ampduretry-pclose-txbf
>
> Yes, ndis. So no easy way to run the same firmware on the 2 OSes.
Indeed. I could try building nearly same firmware target. Can you
provide the firmware version as well.
Now reading over your orignal email again:
> If I place both antenna terminals inside the Linux MiniPC case, the
> Linux pings are bad but the Windows pings are fine.
>
> If I place both antenna terminals inside the Windows MiniPC case, it
> is the same: Linux pings are bad, but the Windows pings are fine.
>
> And when the Linux antenna is placed outside of both cases, the Linux
> pings are fine. I've repeated these tests a handful of times in quick
> succession to make sure that I'm not going crazy and that this is not
> a case of the problem intermittency causing misleading results. These
> findings appear very solid.
So it picks up something in the PC. Some sources of interference that I
have seen before are USB3 and HDMI. Maybe try to shield those if present
and see if that helps. The nvram contains sensitivity parameters, but as
you stated you are using the same nvram for windows and linux for now we
can rule it out for debugging the issue.
Regards,
Arend
next prev parent reply other threads:[~2018-03-08 10:47 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
2018-02-23 13:49 ` Daniel Drake
2018-03-08 10:47 ` Arend van Spriel [this message]
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=5AA114A9.8050801@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).