linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: "Tamás Szűcs" <tszucs@protonmail.ch>, linux-firmware@kernel.org
Cc: briannorris@chromium.org, francesco@dolcini.it,
	linux-wireless@vger.kernel.org, lukas@wunner.de,
	yu-hao.lin@nxp.com
Subject: Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware git
Date: Wed, 5 Jun 2024 17:47:09 +0200	[thread overview]
Message-ID: <20240605174709.5043af8f@akair> (raw)
In-Reply-To: <_pNnwoI9WHlb2EY635KdIv6t_goU-ZYp9Vav31jkFOCf9fCE9EeKdyCea2m-L8pgfsKIQvODlnQLhQqmWSYip9e6FFZwaJHL5-u5rdOS_kY=@protonmail.ch>

Am Wed, 05 Jun 2024 14:43:53 +0000
schrieb Tamás Szűcs <tszucs@protonmail.ch>:

> 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.
> 
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.

> 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

  reply	other threads:[~2024-06-05 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 14:00 mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware git Andreas Kemnade
2024-06-05 14:43 ` Tamás Szűcs
2024-06-05 15:47   ` Andreas Kemnade [this message]
2024-06-06 10:18     ` Francesco Dolcini
2024-06-06 13:49       ` Lukas Wunner
2024-06-12  2:17       ` [EXT] " David Lin
2024-06-12  6:47         ` Francesco Dolcini
2024-06-17  2:13           ` David Lin
2024-11-16 21:41             ` Andreas Kemnade
2024-06-12  7:40         ` Andreas Kemnade
2024-06-14  5:42           ` Neeraj Sanjay Kale

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=20240605174709.5043af8f@akair \
    --to=andreas@kemnade.info \
    --cc=briannorris@chromium.org \
    --cc=francesco@dolcini.it \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=tszucs@protonmail.ch \
    --cc=yu-hao.lin@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).