linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Cao <james.cao@nxp.com>
To: "Pali Rohár" <pali@kernel.org>,
	"Prashanth Ranganathan" <prashanthkrishnan.ranganathan@nxp.com>
Cc: "Sharvari Harisangam" <sharvari.harisangam@nxp.com>,
	"Rakesh Parmar" <rakesh.parmar@nxp.com>,
	"Cathy Luo" <xiaohua.luo@nxp.com>,
	"Linux Firmware" <linux-firmware@kernel.org>,
	"Linux Wireless" <linux-wireless@vger.kernel.org>,
	"Gérald Kerma" <gandalf@gk2.net>,
	"Josh Boyer" <jwboyer@kernel.org>
Subject: Re: [EXT] Re: mwifiex 1.0 (16.68.10.p159) - PCIEUSB-8997 firmware is buggy
Date: Wed, 26 Jan 2022 23:28:48 +0000	[thread overview]
Message-ID: <AS8PR04MB8419C8377C9458ADA340AC24E0209@AS8PR04MB8419.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20220120193041.fmmmd77ingjvyqe4@pali>

[-- Attachment #1: Type: text/plain, Size: 8057 bytes --]

Hi Pali,

NXP doesn't have a plan to support mwifiex driver anymore. How should we handle this kind of retired project in upstream?

Thanks,
James

________________________________
From: Pali Rohár <pali@kernel.org>
Sent: Thursday, January 20, 2022 11:30 AM
To: Prashanth Ranganathan <prashanthkrishnan.ranganathan@nxp.com>
Cc: Sharvari Harisangam <sharvari.harisangam@nxp.com>; Rakesh Parmar <rakesh.parmar@nxp.com>; Cathy Luo <xiaohua.luo@nxp.com>; James Cao <james.cao@nxp.com>; Linux Firmware <linux-firmware@kernel.org>; Linux Wireless <linux-wireless@vger.kernel.org>; Gérald Kerma <gandalf@gk2.net>; Ganapathi Bhat <ganapathi017@gmail.com>; Josh Boyer <jwboyer@kernel.org>
Subject: [EXT] Re: mwifiex 1.0 (16.68.10.p159) - PCIEUSB-8997 firmware is buggy

Caution: EXT Email

Hello Prashanth!

Thank you for reply. Did you have a time to check this issue?

Gérald did a great testing which shows that version W16.68.1.p195 and
higher of pcieuart8997_combo_v4.bin firmware does not work.

On Friday 14 January 2022 17:11:18 Prashanth Ranganathan wrote:
> Hi Pali,
> Please allow me to check this and respond ASAP.
> Best,
> Prashanth
> ________________________________
> From: Pali Rohár <pali@kernel.org>
> Sent: Friday, January 14, 2022 9:00 AM
> To: Sharvari Harisangam <sharvari.harisangam@nxp.com>; Rakesh Parmar <rakesh.parmar@nxp.com>; Cathy Luo <xiaohua.luo@nxp.com>; Prashanth Ranganathan <prashanthkrishnan.ranganathan@nxp.com>; James Cao <james.cao@nxp.com>
> Cc: Linux Firmware <linux-firmware@kernel.org>; Linux Wireless <linux-wireless@vger.kernel.org>; Gérald Kerma <gandalf@gk2.net>; Ganapathi Bhat <ganapathi017@gmail.com>; Josh Boyer <jwboyer@kernel.org>
> Subject: [EXT] Re: mwifiex 1.0 (16.68.10.p159) - PCIEUSB-8997 firmware is buggy
>
> Caution: EXT Email
>
> NXP people: Sharvari, Rakesh, Cathy, Zheng: could you please look at
> this issue? It is really serous!
>
> On Monday 27 September 2021 09:47:23 Josh Boyer wrote:
> > On Sun, Sep 26, 2021 at 6:43 AM Pali Rohár <pali@kernel.org> wrote:
> > >
> > > Hello Josh, Sharvari and other from NXP!
> > >
> > > On Saturday 25 September 2021 19:23:48 Gérald Kerma wrote:
> > > > Correcting old marvell address to new nxp...
> > > >
> > > > Le 25/09/2021 à 19:19, Gérald Kerma a écrit :
> > > > > Héllo All,
> > > > >
> > > > > I made some few tests on EspressoBin-Ultra from GlobalScaleTechnologies,
> > > > > because of problem with the WiFi.
> > > > >
> > > > > I have done some quick tests on all the firmware of PCIEUSB-8997 using
> > > > > the pcieuart8997_combo_v4.bin on OpenWrt 21.02.x
> > > > >
> > > > > Here is a summary of the tests :
> > > > > - W16.68.10.p159 = KO
> > > > > - W16.68.1.p195 = KO
> > > > > - V16.68.1.p145 = OK
> > > > > - 16.68.1.p140 = OK
> > > > > - 16.68.1.p133 = OK
> > > > > - 16.68.1.p97 = OK
> > > > > - 16.68.1.p70 = KO
> > >
> > > From this user test result can be seen that last two versions of
> > > pcieusb8997_combo_v4.bin firmware file for 8997 wifi+bt card with
> > > official mainline linux kernel driver mwifiex were not properly tested
> > > internally in NXP and are causing serious issues which make 8997 card
> > > basically unusable.
> > >
> > > Sharvari and other NXP developers: Do you have some internal testing of
> > > this pcieusb8997_combo_v4.bin firmware for PCIe+USB variant of 8997
> > > wifi chips? Or are you aware of this issue and do you have in NXP some
> > > workaround for it (e.g. at driver level)? Could you please look at this
> > > serious issue and try to debug firmware and release a new version, as
> > > this is obvious fatal error in firmware itself?
> > >
> > > Josh, how you in linux-firmware repository handle such, I must say,
> > > "fatal issues"? Wait for vendor fixes or revert problematic commits? Or
> > > something else?
> >
> > We can revert if we need to, but I think it's not quite that simple.
> >
> > > Because when users starts upgrading linux-firmware packages in their
> > > downstream distributions then basically wifi cards on this 8997 chips
> > > with official mwifiex driver stops working.
> >
> > The first broken version was committed in Feb of 2019.  That's
> > approaching 3 years ago.  Given that this is binary firmware, I have
> > no idea what else may or may not be included in the updates in the
> > meantime.
> >
> > josh
>
> Josh, as Gérald wrote, current binary in linux-firmware repository is
> unusable. And there is no reply from NXP for 3 months.
>
> You are right that nobody knows what is in firmware binary, but working
> binary is at least usable than non-working binary.
>
> So I would really suggest to start reverting non-working firmware files
> if NXP does not respond in few days.
>
> Gérald, what is your opinion? Do you see other way how to make mainline
> linux driver work (again)?
>
> > > > > REF (and all details of tests) :
> > > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNXP%2Fmwifiex-firmware%2Fissues%2F1&amp;data=04%7C01%7Cjames.cao%40nxp.com%7C09714bf302224e66a34c08d9dc4b5bb5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637783038495772224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Y6a7lP%2B%2FXwPWGZARx3c99qV3ZFundY0QtfjmC1mYn4%3D&amp;reserved=0
> > > > >
> > > > >
> > > > > Broken firmware :
> > > > >
> > > > > Version |W16.68.1.p195| of |pcieusb8997_combo_v4.bin| was included into
> > > > > linux-firmware repository by this pull request:
> > > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fall%2FCA%2B5PVA5yQbjg3vaT7F8120B6ngLn7%2BsZC0OWt0KoUiQR9hS4FA%40mail.gmail.com%2F&amp;data=04%7C01%7Cjames.cao%40nxp.com%7C09714bf302224e66a34c08d9dc4b5bb5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637783038495772224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=nbzs6YB%2Fyjdp9zJR1PQyZ2prUtPOjthVewIhBCwcqdg%3D&amp;reserved=0
> > > > > <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fall%2FCA%2B5PVA5yQbjg3vaT7F8120B6ngLn7%2BsZC0OWt0KoUiQR9hS4FA%40mail.gmail.com%2F&amp;data=04%7C01%7Cjames.cao%40nxp.com%7C09714bf302224e66a34c08d9dc4b5bb5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637783038495772224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=nbzs6YB%2Fyjdp9zJR1PQyZ2prUtPOjthVewIhBCwcqdg%3D&amp;reserved=0>
> > > > >
> > > > > And latest version |W16.68.10.p159| of |pcieusb8997_combo_v4.bin| by
> > > > > this pull request:
> > > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Flinux-firmware%2FCA%2B5PVA5on7%2BCRtEV7tThPxgucwt3W9i-tEXm4cgH-AmMB-Jrtg%40mail.gmail.com%2F&amp;data=04%7C01%7Cjames.cao%40nxp.com%7C09714bf302224e66a34c08d9dc4b5bb5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637783038495772224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=6wktlFLItFxzOdYcgTI2Rs9x3PamVJyfWtaNJU0o0bw%3D&amp;reserved=0
> > > > > <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Flinux-firmware%2FCA%2B5PVA5on7%2BCRtEV7tThPxgucwt3W9i-tEXm4cgH-AmMB-Jrtg%40mail.gmail.com%2F&amp;data=04%7C01%7Cjames.cao%40nxp.com%7C09714bf302224e66a34c08d9dc4b5bb5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637783038495772224%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=6wktlFLItFxzOdYcgTI2Rs9x3PamVJyfWtaNJU0o0bw%3D&amp;reserved=0>
> > > > >
> > > > > Olders looks to works better.
> > > > >
> > > > > In quick tests, they allow more than 1 clients at a time !
> > > > >
> > > > > I am still testing the V16.68.1.p145 and report the results after some
> > > > > longer use...
> > > > >
> > > > > Hopes it will help...
> > > > > Regards,
> > > > > Gérald Kerma
> > > > > gandalf(at)gk2(dot)net
> > > >

[-- Attachment #2: Type: text/html, Size: 13611 bytes --]

  reply	other threads:[~2022-01-26 23:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 17:19 mwifiex 1.0 (16.68.10.p159) - PCIEUSB-8997 firmware is buggy Gérald Kerma
2021-09-25 17:23 ` Gérald Kerma
2021-09-26 10:43   ` Pali Rohár
2021-09-27 13:47     ` Josh Boyer
2021-09-28 11:26       ` Gérald Kerma
2021-09-28 11:30         ` Gérald Kerma
2021-10-09 11:07       ` Pali Rohár
2021-10-09 12:36         ` Josh Boyer
2021-10-09 12:45           ` Pali Rohár
2022-01-14 17:00       ` Pali Rohár
2022-01-14 17:11         ` [EXT] " Prashanth Ranganathan
2022-01-20 19:30           ` Pali Rohár
2022-01-26 23:28             ` James Cao [this message]
2022-01-27  1:13               ` [EXT] " Gérald Kerma
2022-01-27 12:15               ` Pali Rohár
2022-01-27 14:50                 ` Gérald Kerma
2022-01-28  0:58                   ` [EXT] " James Cao
2022-01-28  8:12                     ` Gérald Kerma
2022-02-11 11:28                     ` Pali Rohár
2022-01-14 18:32         ` Gérald Kerma

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=AS8PR04MB8419C8377C9458ADA340AC24E0209@AS8PR04MB8419.eurprd04.prod.outlook.com \
    --to=james.cao@nxp.com \
    --cc=gandalf@gk2.net \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=prashanthkrishnan.ranganathan@nxp.com \
    --cc=rakesh.parmar@nxp.com \
    --cc=sharvari.harisangam@nxp.com \
    --cc=xiaohua.luo@nxp.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).