Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CAA=hcWQFNOeycXFPhrtHcQG3V8fWSShNRuAi49jtv8h1fPVUuQ@mail.gmail.com>
 <8ef5d73a-6293-a6c5-6bbb-b130266a8f0b@broadcom.com> <CAA=hcWQ_FVTVfRe91z1yHXMBLkkhi0eTq-9Lw3Tg=X6OS5Ku-Q@mail.gmail.com>
In-Reply-To: <CAA=hcWQ_FVTVfRe91z1yHXMBLkkhi0eTq-9Lw3Tg=X6OS5Ku-Q@mail.gmail.com>
From:   Brian Norris <briannorris@chromium.org>
Date:   Wed, 6 Apr 2022 13:15:44 -0700
Message-ID: <CA+ASDXPXCLjSL+mKKn-vh0fx0jdGBN-HOSDh4Dvy+93HSdRfBg@mail.gmail.com>
Subject: Re: Support for bcm43364 wireless chipset in brcm80211/brcmfmac
To:     Jupiter <jupiter.hce@gmail.com>
Cc:     Arend van Spriel <arend.vanspriel@broadcom.com>,
        "David S. Miller" <davem@davemloft.net>,
        Sean Lanigan <sean@lano.id.au>,
        Kalle Valo <kvalo@codeaurora.org>,
        linux-wireless <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Apr 6, 2022 at 1:09 PM Jupiter <jupiter.hce@gmail.com> wrote:
> Our original design was using Marvell Avastar 88W8801
> chipset, the driver mwifiex and wifiex_sdio worked well for kernel 4,
> but after NXP acquired Marvell wireless sector, NXP stopped supporting
> mainline Linux, the kernel 5 mwifiex cannot communicate to 88W8801
> chipset firmware, we were told to use the proprietary Linux driver
> sources which is incompatible to our Yocto / OE build system, we have
> no choice but to change the WiFi module.

Despite what corporations tell you, mainline Linux shouldn't be
dropping support for things just because the corporation moved on. If
you can track down the mwifiex regression (e.g., with bisection),
there's a chance we can fix it. I still see
SDIO_DEVICE_ID_MARVELL_8801 listed in the upstream driver, FWIW.

Unfortunately, without anyone paying attention (Marvell, NXP, ... or
you) that has the hardware, it can be hard to guarantee things stay
working. Hint: while I have (and care about) several Marvell chips, I
don't have that one.

Brian