Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dominique MARTINET <dominique.martinet@atmark-techno.com>
To: Sharvari Harisangam <sharvari.harisangam@nxp.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Amitkumar Karwar" <amitkarwar@gmail.com>,
	"Jonas Dreßler" <verdre@v0yd.nl>, "Takashi Iwai" <tiwai@suse.de>,
	"Tsuchiya Yuto" <kitakar@gmail.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Lee Jones" <lee.jones@linaro.org>,
	"Kalle Valo" <kvalo@codeaurora.org>,
	"Xinming Hu" <huxinming820@gmail.com>,
	"Ganapathi Bhat" <ganapathi017@gmail.com>
Subject: Re: [EXT] Re: mwifiex cmd timeout on one pci variant
Date: Wed, 8 Sep 2021 14:56:24 +0900	[thread overview]
Message-ID: <YThQiMn7YHzPRwnJ@atmark-techno.com> (raw)
In-Reply-To: <AM0PR04MB4529E0C28F43288E189D8F50FCD49@AM0PR04MB4529.eurprd04.prod.outlook.com>

Sharvari Harisangam wrote on Wed, Sep 08, 2021 at 05:45:53AM +0000:
> Use firmware from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mrvl
> for mwifiex driver.

Thanks, that's the first firmware I was using; it's currently at
16.68.1.p179 which is why I'm surprised Jonas said the latest would be
15.68.19.p21.

I think it's just a different variant of the driver now though,
a binary grep matches 15.68.19.p21 for pcie8897_uapsta.bin but I my
driver loads pcieuart8997_combo_v4.bin
I hadn't noticed the first number didn't match, but that likely confirms
it.

Sorry for the noise on firmware version, I'm still interested in
understanding why the command timeouts.
-- 
Dominique Martinet

  reply	other threads:[~2021-09-08  5:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  4:43 mwifiex cmd timeout on one pci variant Dominique MARTINET
2021-09-08  5:36 ` Dominique MARTINET
2021-09-08  5:45   ` [EXT] " Sharvari Harisangam
2021-09-08  5:56     ` Dominique MARTINET [this message]
2021-09-14 10:11       ` Jonas Dreßler
2021-09-15  1:43         ` Dominique MARTINET
2021-09-15 10:06           ` Jonas Dreßler
2021-09-08 16:56 ` Brian Norris
2021-09-08 23:48   ` Dominique MARTINET

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=YThQiMn7YHzPRwnJ@atmark-techno.com \
    --to=dominique.martinet@atmark-techno.com \
    --cc=amitkarwar@gmail.com \
    --cc=arnd@arndb.de \
    --cc=ganapathi017@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=huxinming820@gmail.com \
    --cc=kitakar@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sharvari.harisangam@nxp.com \
    --cc=tiwai@suse.de \
    --cc=verdre@v0yd.nl \
    /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