Return-path: Received: from mail-qk0-f180.google.com ([209.85.220.180]:33419 "EHLO mail-qk0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934574AbeCHKrJ (ORCPT ); Thu, 8 Mar 2018 05:47:09 -0500 Received: by mail-qk0-f180.google.com with SMTP id f25so6272311qkm.0 for ; Thu, 08 Mar 2018 02:47:08 -0800 (PST) Subject: Re: brcmfmac signal/interference issues To: Daniel Drake References: <5A8D36B7.1010201@broadcom.com> <5A8FE4D9.80608@broadcom.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 From: Arend van Spriel Message-ID: <5AA114A9.8050801@broadcom.com> (sfid-20180308_114714_437626_EBCAC0AE) Date: Thu, 8 Mar 2018 11:47:05 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 2/23/2018 2:49 PM, Daniel Drake wrote: > On Fri, Feb 23, 2018 at 12:54 PM, Arend van Spriel > 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