Linux wireless drivers development
 help / color / mirror / Atom feed
From: Andreas Kemnade <andreas@kemnade.info>
To: Brian Norris <briannorris@chromium.org>
Cc: "David Lin" <yu-hao.lin@nxp.com>,
	"Francesco Dolcini" <francesco@dolcini.it>,
	"Neeraj Sanjay Kale" <neeraj.sanjaykale@nxp.com>,
	"Tamás Szűcs" <tszucs@protonmail.ch>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"lukas@wunner.de" <lukas@wunner.de>
Subject: Re: [EXT] Re: mwifiex firmware mrvl/sd8987_uapsta.bin missing in the firmware git
Date: Tue, 29 Sep 2026 15:43:01 +0200	[thread overview]
Message-ID: <20260929154301.7c45c1be@kemnade.info> (raw)
In-Reply-To: <arqp7k55wqW5ZgCV@google.com>

On Mon, 28 Sep 2026 10:54:54 -0700
Brian Norris <briannorris@chromium.org> wrote:

> On Sat, Sep 26, 2026 at 09:00:26AM +0200, Andreas Kemnade wrote:
> > 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.
> 
> > 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.

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

> 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

  reply	other threads:[~2026-09-29 14:22 UTC|newest]

Thread overview: 16+ 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
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
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 [this message]
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=20260929154301.7c45c1be@kemnade.info \
    --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=neeraj.sanjaykale@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