mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware git
Hi,
I am a bit wondering, but there is mrvl/sd8987_uapsta.bin referenced in the driver, but apperently it is not in the firmware git.
seems to apparently work. How to proceed? Should the file be renamed and added to the fw git?
The uartuart8987_bt.bin needed by the btnxpuart driver is there.
It is just nasty to have a driver for a device but some manual matching of firmware
BTW: there is also https://github.com/nxp-imx/imx-firmware/blob/lf-6.6.3_1.0.0/nxp/FwImage_8987/sd8987_wlan.bin
Regards,
Andreas
Hi Andreas,
Excellent point. Please note, that btmrvl_sdio needs an SDIO BT FW. So, mrvl/sd8987_uapsta.bin should preferably be a such a combo FW.
Unfortunately, to my knowledge, none is available publicly. Also, after the acquisition of Marvell IoT, NXP regrettably decided to develop mwifiex downstream, here https://github.com/nxp-imx/mwifiex.
It is what it is. Due to licensing, the FW binary should come from NXP. I cannot arrange that.
Kind regards,
Tamas
Tamás Szűcs
[email protected]
Sent with Proton Mail secure email.
Quoted 17 lines · Andreas Kemnade
Hi,
I am a bit wondering, but there is mrvl/sd8987_uapsta.bin referenced in the driver, but apperently it is not in the firmware git.
seems to apparently work. How to proceed? Should the file be renamed and added to the fw git?
The uartuart8987_bt.bin needed by the btnxpuart driver is there.It is just nasty to have a driver for a device but some manual matching of firmware
BTW: there is also https://github.com/nxp-imx/imx-firmware/blob/lf-6.6.3_1.0.0/nxp/FwImage_8987/sd8987_wlan.bin
Regards,
Andreas
Am Wed, 05 Jun 2024 14:43:53 +0000
schrieb Tamás Szűcs <[email protected]>:
Quoted 5 lines
Hi Andreas,
Excellent point. Please note, that
btmrvl_sdioneeds an SDIO BT FW. So, mrvl/sd8987_uapsta.bin should preferably be a such a combo FW.
as said the firmware here seems to work for me (after renaming):
https://github.com/nxp-imx/imx-firmware/blob/lf-6.6.3_1.0.0/nxp/FwImage_8987/sdiouart8987_combo_v0.bin
I can use bluetooth together with btnxpuart driver and firmware /lib/firmware/nxp/uartuart8987_bt.bin which is officially part of linux-firmware and also in the same directory in the imx-firmware git mentioned above.
Quoted 6 lines
Unfortunately, to my knowledge, none is available publicly. Also, after the acquisition of Marvell IoT, NXP regrettably decided to develop mwifiex downstream, here https://github.com/nxp-imx/mwifiex.
It is what it is. Due to licensing, the FW binary should come from NXP. I cannot arrange that.
Regarding license I found that snippet in nxp/SCR_nxp.txt:
Package: FwImage_8997, FwImage_8987, FwImage_8801,FwImage_9098, FwImage_IW416, FwImage_IW612 Outgoing License:LA_OPT_NXP_Software_License - Production Use, Section 2.3 applies
License File: EULA.txt
Section 2.3 is:
2.3. Additional Distribution License
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Regards,
Andreas
+Neeraj
Hello David, hello Neeraj
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the mwifiex driver).
Thanks,
Francesco
[add more interested parties to cc]
Quoted 11 lines · Francesco Dolcini
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the mwifiex driver).
I'd appreciate if NXP could additionally greenlight addition of:
https://github.com/nxp-imx/imx-firmware/blob/lf-6.6.3_1.0.0/nxp/FwImage_IW416_SD/sdiouartiw416_combo_v0.bin
https://github.com/nxp-imx/imx-firmware/blob/lf-6.6.3_1.0.0/nxp/FwImage_IW416_SD/uartiw416_bt_v0.bin
...to the linux-firmware repo. They're necessary for SD8978 (aka IW416), which has been supported by mwifiex since commit bba047f15851 ("wifi:
mwifiex: Support SD8978 chipset").
Back in the day when I submitted that commit, I concurrently reached out to NXP. Sherry Sun kindly responded that Dinesh Phatak and Pankaj Razdan need to confirm upstreaming into linux-firmware (both +cc).
The problem is that mwifiex firmware originating from
https://github.com/NXP/mwifiex-firmware/
is available under a simple 3-clause licence, but only contains outdated firmware for older chips.
More recent firmware available from
https://github.com/nxp-imx/imx-firmware
seems to be distributed under different and much longer licensing terms:
https://github.com/nxp-imx/imx-firmware/blob/lf-6.6.3_1.0.0/LICENSE.txt
So I think we need confirmation from NXP before we can add the firmware to the linux-firmware repo.
Thanks,
Lukas
Quoted 24 lines
From: Francesco Dolcini <[email protected]>
Sent: Thursday, June 6, 2024 6:19 PM
To: Andreas Kemnade <[email protected]>; David Lin <[email protected]>; Neeraj Sanjay Kale <[email protected]>
Cc: Tamás Szűcs <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: [EXT] Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware gitCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
+Neeraj
Hello David, hello Neeraj
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Quoted 8 lines
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the mwifiex driver).
Thanks,
Francesco
I am not responsible for firmware release.
You can get updated firmware from https://github.com/nxp-imx/imx-firmware/.
Normally the firmware will be merged to NXP Yocto project.
Thanks,
David
Hello David,
Quoted 6 lines · David Lin
Quoted 6 lines
From: Francesco Dolcini <[email protected]>
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Quoted 8 lines
Quoted 5 lines
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the mwifiex driver).
I am not responsible for firmware release.
You can get updated firmware from https://github.com/nxp-imx/imx-firmware/.
Yes, I am aware of both, and most of the people in this thread is aware of the second.
I was wondering if you could facilitate within NXP having these firmware files added to the linux firmware git repository, where they should be for various reasons. To whom should I write such a request? Can you help in any way?
Francesco
Quoted 43 lines
From: Francesco Dolcini <[email protected]>
Sent: Wednesday, June 12, 2024 2:48 PM
To: David Lin <[email protected]>
Cc: Francesco Dolcini <[email protected]>; Andreas Kemnade <[email protected]>; Neeraj Sanjay Kale <[email protected]>; Tamás Szűcs <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [EXT] Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware gitCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
Hello David,
Quoted 11 lines · David Lin
Quoted 11 lines
From: Francesco Dolcini <[email protected]> On Wed, Jun 05, 2024
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the
mwifiex driver).
Quoted 3 lines
I am not responsible for firmware release.
You can get updated firmware fromhttps://github.co/
m%2Fnxp-imx%2Fimx-firmware%2F&data=05%7C02%7Cyu-hao.lin%40nxp.co m%7C10acf638ebf04b0979ed08dc8aab99d5%7C686ea1d3bc2b4c6fa92cd99c5 c301635%7C0%7C0%7C638537716818815780%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3 D%7C0%7C%7C%7C&sdata=ZrU82HbKZ%2Ff87IG2tgInfq7kbyCuV8PcksxvTWiM HtQ%3D&reserved=0.
Yes, I am aware of both, and most of the people in this thread is aware of the second.
Quoted 5 lines
I was wondering if you could facilitate within NXP having these firmware files added to the linux firmware git repository, where they should be for various reasons. To whom should I write such a request? Can you help in any way?
Francesco
I reported this issue just like Neeraj did.
David
Hi,
Am Mon, 17 Jun 2024 02:13:22 +0000
schrieb David Lin <[email protected]>:
Quoted 43 lines
Quoted 43 lines
From: Francesco Dolcini <[email protected]>
Sent: Wednesday, June 12, 2024 2:48 PM
To: David Lin <[email protected]>
Cc: Francesco Dolcini <[email protected]>; Andreas Kemnade <[email protected]>; Neeraj Sanjay Kale <[email protected]>; Tamás Szűcs <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [EXT] Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware gitCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
Hello David,
Quoted 11 lines · David Lin
Quoted 11 lines
From: Francesco Dolcini <[email protected]> On Wed, Jun 05, 2024
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the
mwifiex driver).
Quoted 3 lines
I am not responsible for firmware release.
You can get updated firmware fromhttps://github.co/
m%2Fnxp-imx%2Fimx-firmware%2F&data=05%7C02%7Cyu-hao.lin%40nxp.co m%7C10acf638ebf04b0979ed08dc8aab99d5%7C686ea1d3bc2b4c6fa92cd99c5 c301635%7C0%7C0%7C638537716818815780%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3 D%7C0%7C%7C%7C&sdata=ZrU82HbKZ%2Ff87IG2tgInfq7kbyCuV8PcksxvTWiM HtQ%3D&reserved=0.
Yes, I am aware of both, and most of the people in this thread is aware of the second.
Quoted 8 lines
Quoted 5 lines
I was wondering if you could facilitate within NXP having these firmware files added to the linux firmware git repository, where they should be for various reasons. To whom should I write such a request? Can you help in any way?
Francesco
I reported this issue just like Neeraj did.
any update on this topic?
Regards,
Andreas
Quoted 43 lines · On Mon, 17 Jun 2024 02:13:22 +0000 David Lin <[email protected]> wrote:
Quoted 43 lines
From: Francesco Dolcini <[email protected]>
Sent: Wednesday, June 12, 2024 2:48 PM
To: David Lin <[email protected]>
Cc: Francesco Dolcini <[email protected]>; Andreas Kemnade <[email protected]>; Neeraj Sanjay Kale <[email protected]>; Tamás Szűcs <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: [EXT] Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware gitCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
Hello David,
Quoted 11 lines · David Lin
Quoted 11 lines
From: Francesco Dolcini <[email protected]> On Wed, Jun 05, 2024
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the
mwifiex driver).
Quoted 3 lines
I am not responsible for firmware release.
You can get updated firmware fromhttps://github.co/
m%2Fnxp-imx%2Fimx-firmware%2F&data=05%7C02%7Cyu-hao.lin%40nxp.co m%7C10acf638ebf04b0979ed08dc8aab99d5%7C686ea1d3bc2b4c6fa92cd99c5 c301635%7C0%7C0%7C638537716818815780%7CUnknown%7CTWFpbGZsb3d 8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3 D%7C0%7C%7C%7C&sdata=ZrU82HbKZ%2Ff87IG2tgInfq7kbyCuV8PcksxvTWiM HtQ%3D&reserved=0.
Yes, I am aware of both, and most of the people in this thread is aware of the second.
Quoted 8 lines
Quoted 5 lines
I was wondering if you could facilitate within NXP having these firmware files added to the linux firmware git repository, where they should be for various reasons. To whom should I write such a request? Can you help in any way?
Francesco
I reported this issue just like Neeraj did.
This thing seems to be stalled.
How is the most practical way to deal with the situation? For people building OE images for machines with these devices it seems clear. But if you do not spread full images, but have an archive of packages.
Lets say the Alpine linux distribution.
The License terms have in 2.3(b):
"(b) to copy and distribute as needed, solely in connection with an
Authorized System and for use in combination with a NXP Product,"
If I read it correctly, the firmware cannot life in such a repository, since the repository is used by different machines. Is my interpretation correct? So would a downloader in a post-install hook be an alternative?
Regards,
Andreas
Quoted 6 lines · Andreas Kemnade
The License terms have in 2.3(b):
"(b) to copy and distribute as needed, solely in connection with an
Authorized System and for use in combination with a NXP Product,"If I read it correctly, the firmware cannot life in such a repository, since the repository is used by different machines. Is my interpretation correct?
I'm no expert and am not providing legal advice.
I see there is some roughly similar (but a little weaker-sounding) language in some existing linux-firmware licenses. e.g., "permitted solely operating in conjunction with <company> authorized products".
I also see the linux-firmware README only says:
Your commit **must** contain a Signed-Off-By: from someone authoritative on the licensing of the firmware in question (i.e. from within the company that owns the code).
I take that to mean that linux-firmware doesn't really try to own the licensing rules. They defer to the company that owns the IP.
So if NXP wants to submit things to linux-firmware (or "sign off" and hand it to someone else), they might be able to do so. YMMV if you're not an NXP employee though.
Brian
Quoted 7 lines · On Fri, 25 Sep 2026 09:27:35 -0700 Brian Norris <[email protected]>…
Quoted 6 lines · Andreas Kemnade
The License terms have in 2.3(b):
"(b) to copy and distribute as needed, solely in connection with an
Authorized System and for use in combination with a NXP Product,"If I read it correctly, the firmware cannot life in such a repository, since the repository is used by different machines. Is my interpretation correct?
re-establishing context again: "such a repository" means that fw packages as e.g. alpine packages and then put into the official alpine repositiory.
Quoted 3 lines
I'm no expert and am not providing legal advice.
I am not either, but there are NXP people in CC hoping to say something more official or finally un-stall this issue.
Quoted 4 lines
I see there is some roughly similar (but a little weaker-soundging) language in some existing linux-firmware licenses. e.g., "permitted solely operating in conjunction with <company> authorized products".
Often it is restricting *use* not *distribution*.
Quoted 9 lines
I also see the linux-firmware README only says:
Your commit **must** contain a
Signed-Off-By:from someone authoritative on the licensing of the firmware in question (i.e. from within the company that owns the code).I take that to mean that linux-firmware doesn't really try to own the licensing rules. They defer to the company that owns the IP.
There are rules what licenses might forbid and what not in LICENSE-CRITERIA.md. At least submitting it to the firmware repo (so from NXP sight a third party repo) sounds like some permission for distribution.
Regards,
Andreas
Quoted 1 line · Andreas Kemnade
There are rules what licenses might forbid and what not in LICENSE-CRITERIA.md.
Ohhh, nice. I was looking for exactly such a file, but I was looking at a too-old copy of linux-firmware.git -- that seems to have appeared in the last few months.
Quoted 2 lines
At least submitting it to the firmware repo (so from NXP sight a third party repo) sounds like some permission for distribution.
Reading that doc: actually, no, that doc seems to suggest otherwise. It specifically delineates various "terms that will cause rejection", and it seems the current NXP license triggers several of those. NXP would almost certainly need to provide an updated license, not just a sign-off with their existing license.
This seems entirely up to NXP to unblock. If they want to work within the open source community, then they need to learn to work with the rules of that community.
Brian
Quoted 11 lines · On Mon, 28 Sep 2026 10:54:54 -0700 Brian Norris <[email protected]>…
Quoted 1 line · Andreas Kemnade
There are rules what licenses might forbid and what not in LICENSE-CRITERIA.md.
Ohhh, nice. I was looking for exactly such a file, but I was looking at a too-old copy of linux-firmware.git -- that seems to have appeared in the last few months.
Quoted 2 lines
At least submitting it to the firmware repo (so from NXP sight a third party repo) sounds like some permission for distribution.
Reading that doc: actually, no, that doc seems to suggest otherwise. It
Maybe I was a bit unclear here. If it is submitted and accepted it feels like some more safety.
Quoted 5 lines
specifically delineates various "terms that will cause rejection", and it seems the current NXP license triggers several of those. NXP would almost certainly need to provide an updated license, not just a sign-off with their existing license.
There are two licenses there: The one in the linux-firmware git repo and the one in NXP's own firmware repo. But both would probably cause rejection nowadays.
Quoted 4 lines
This seems entirely up to NXP to unblock. If they want to work within the open source community, then they need to learn to work with the rules of that community.
Yes, the only thing others could do is to nag them about it.
Regards,
Andreas
Quoted 30 lines · On Wed, 12 Jun 2024 02:17:46 +0000 David Lin <[email protected]> wrote:
Quoted 30 lines
From: Francesco Dolcini <[email protected]>
Sent: Thursday, June 6, 2024 6:19 PM
To: Andreas Kemnade <[email protected]>; David Lin <[email protected]>; Neeraj Sanjay Kale <[email protected]>
Cc: Tamás Szűcs <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]
Subject: [EXT] Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware gitCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
+Neeraj
Hello David, hello Neeraj
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the mwifiex driver).
Quoted 9 lines
Quoted 2 lines
Thanks,
FrancescoI am not responsible for firmware release.
You can get updated firmware from https://github.com/nxp-imx/imx-firmware/.
Normally the firmware will be merged to NXP Yocto project.
yes, I think most of us are aware of this.
So what is the problem: E.g. I have bought a new device, ported a linux distro to it, ok, for my personal use, I can just download the firmware from mentioned link. So now I want to pave the road for others so that wifi "just works" So the question is about redistributing the firmware:
Citing License:
"(b) to copy and distribute as needed, solely in connection with an
Authorized System and for use in combination with a NXP Product, non-confidential NXP information provided as part of the Licensed Software for the purpose of maintaining and supporting Authorized Systems with which the Licensed Software is integrated."
to me it looks like the firmware might not allowed to be part of a linux distribution if that linux distribution is not just for one device. So an official permission to do so is really helpful. The most clearest thing would be an addition of the files to the official linux firmware repo (git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
by some NXP people.
Regards,
Andreas
++ Pushkar, Pete, Amit, Pankaj in CC
Hi Francesco,
I am not responsible for mwifiex or wifi firmware aspects, but I have forwarded this query internally within NXP and added few stakeholders in CC who can comment in this regards.
Thanks,
Neeraj
Quoted 51 lines
Quoted 7 lines
Quoted 7 lines
Hello David, hello Neeraj
Quoted 3 lines · Andreas Kemnade
But that is all legalese and I am not a lawyer... Best is of course something officially added from NXP. No idea if it can be done otherwise. How to make NXP add something?
Quoted 5 lines
Quoted 5 lines
Would it be possible for you to get these firmware files added to the official linux-firmware git repo?
I am not using sd8987 myself, from what I read in the thread probably some file name would need to be corrected (I would say in the
mwifiex driver).
Quoted 7 lines
Quoted 3 lines
Thanks,
FrancescoI am not responsible for firmware release.
You can get updated firmware from
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.
com%2Fnxp-imx%2Fimx- firmware%2F&data=05%7C02%7Cneeraj.sanjaykale%40nxp.com%7Cf6a593f3 0cbd4db4c25708dc8ab2e6c3%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0 %7C0%7C638537748179838808%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C40000 %7C%7C%7C&sdata=3VpeUrG20NMjgFHNaN32m11zeyBobUX%2BBoeipSEUnz s%3D&reserved=0.Quoted 3 lines
Normally the firmware will be merged to NXP Yocto project.
yes, I think most of us are aware of this.
So what is the problem: E.g. I have bought a new device, ported a linux distro to it, ok, for my personal use, I can just download the firmware from mentioned link. So now I want to pave the road for others so that wifi "just works" So the question is about redistributing the firmware:Citing License:
"(b) to copy and distribute as needed, solely in connection with an
Authorized System and for use in combination with a NXP Product, non- confidential NXP information provided as part of the Licensed Software for the purpose of maintaining and supporting Authorized Systems with which the Licensed Software is integrated."to me it looks like the firmware might not allowed to be part of a linux distribution if that linux distribution is not just for one device. So an official permission to do so is really helpful. The most clearest thing would be an addition of the files to the official linux firmware repo
(git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git)
by some NXP people.