Linux-Firmware Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Francesco Dolcini <francesco@dolcini.it>,
	Sherry Sun <sherry.sun@nxp.com>,
	Dinesh Phatak <dinesh.phatak@nxp.com>,
	Pankaj Razdan <pankaj.razdan@nxp.com>
Cc: "Andreas Kemnade" <andreas@kemnade.info>,
	yu-hao.lin@nxp.com, "Neeraj Kale" <neeraj.sanjaykale@nxp.com>,
	"Tamás Sz??cs" <tszucs@protonmail.ch>,
	linux-firmware@kernel.org, briannorris@chromium.org,
	linux-wireless@vger.kernel.org,
	"Nicolai Buchwitz" <n.buchwitz@kunbus.com>,
	"Philipp Rosenberger" <p.rosenberger@kunbus.com>,
	"Lino Sanfilippo" <LinoSanfilippo@gmx.de>
Subject: Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware git
Date: Thu, 6 Jun 2024 15:49:53 +0200	[thread overview]
Message-ID: <ZmG-gZ306WXZUa-n@wunner.de> (raw)
In-Reply-To: <20240606101839.GA76158@francesco-nb>

[add more interested parties to cc]

On Thu, Jun 06, 2024 at 12:18:39PM +0200, Francesco Dolcini wrote:
> On Wed, Jun 05, 2024 at 05:47:09PM +0200, Andreas Kemnade wrote:
> > 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

  reply	other threads:[~2024-06-06 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240605160013.6bea8d4d@aktux>
     [not found] ` <_pNnwoI9WHlb2EY635KdIv6t_goU-ZYp9Vav31jkFOCf9fCE9EeKdyCea2m-L8pgfsKIQvODlnQLhQqmWSYip9e6FFZwaJHL5-u5rdOS_kY=@protonmail.ch>
2024-06-05 15:47   ` mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware git Andreas Kemnade
2024-06-06 10:18     ` Francesco Dolcini
2024-06-06 13:49       ` Lukas Wunner [this message]
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
2026-09-25 14:58             ` Andreas Kemnade
2026-09-25 16:27               ` Brian Norris
2026-09-26  7:00                 ` Andreas Kemnade
2026-09-28 17:54                   ` Brian Norris
2026-09-29 13:43                     ` 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=ZmG-gZ306WXZUa-n@wunner.de \
    --to=lukas@wunner.de \
    --cc=LinoSanfilippo@gmx.de \
    --cc=andreas@kemnade.info \
    --cc=briannorris@chromium.org \
    --cc=dinesh.phatak@nxp.com \
    --cc=francesco@dolcini.it \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=n.buchwitz@kunbus.com \
    --cc=neeraj.sanjaykale@nxp.com \
    --cc=p.rosenberger@kunbus.com \
    --cc=pankaj.razdan@nxp.com \
    --cc=sherry.sun@nxp.com \
    --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