From: "Gérald Kerma" <gandalf@gk2.net>
To: linux-firmware@kernel.org, Josh Boyer <jwboyer@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Sharvari Harisangam <sharvari.harisangam@nxp.com>,
Rakesh Parmar <rakesh.parmar@nxp.com>,
Cathy Luo <xiaohua.luo@nxp.com>,
pali@kernel.org, zhiyuan.yang@nxp.com,
prashanthkrishnan.ranganathan@nxp.com, ganapathi.bhat@nxp.com,
zheng.cao@nxp.com, rakesh.parmar@nxp.com, xiaohua.luo@nxp.com
Subject: Re: mwifiex 1.0 (16.68.10.p159) - PCIEUSB-8997 firmware is buggy
Date: Sat, 25 Sep 2021 19:23:48 +0200 [thread overview]
Message-ID: <fe75e8f2-6f12-052a-81ed-38122b87f1f6@gk2.net> (raw)
In-Reply-To: <edeb34bc-7c85-7f1d-79e4-e3e21df86334@gk2.net>
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
>
> REF (and all details of tests) :
> https://github.com/NXP/mwifiex-firmware/issues/1
>
>
> Broken firmware :
>
> Version |W16.68.1.p195| of |pcieusb8997_combo_v4.bin| was included into
> linux-firmware repository by this pull request:
> https://lore.kernel.org/all/CA+5PVA5yQbjg3vaT7F8120B6ngLn7+sZC0OWt0KoUiQR9hS4FA@mail.gmail.com/
> <https://lore.kernel.org/all/CA+5PVA5yQbjg3vaT7F8120B6ngLn7+sZC0OWt0KoUiQR9hS4FA@mail.gmail.com/>
>
> And latest version |W16.68.10.p159| of |pcieusb8997_combo_v4.bin| by
> this pull request:
> https://lore.kernel.org/linux-firmware/CA+5PVA5on7+CRtEV7tThPxgucwt3W9i-tEXm4cgH-AmMB-Jrtg@mail.gmail.com/
> <https://lore.kernel.org/linux-firmware/CA+5PVA5on7+CRtEV7tThPxgucwt3W9i-tEXm4cgH-AmMB-Jrtg@mail.gmail.com/>
>
> 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
next prev parent reply other threads:[~2021-09-25 17:44 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 [this message]
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 ` [EXT] " James Cao
2022-01-27 1:13 ` 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=fe75e8f2-6f12-052a-81ed-38122b87f1f6@gk2.net \
--to=gandalf@gk2.net \
--cc=ganapathi.bhat@nxp.com \
--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 \
--cc=zheng.cao@nxp.com \
--cc=zhiyuan.yang@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 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.