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: Sat, 26 Sep 2026 09:00:26 +0200 [thread overview]
Message-ID: <20260926090026.22b00f57@kemnade.info> (raw)
In-Reply-To: <arag95IJHR5FiFo9@google.com>
On Fri, 25 Sep 2026 09:27:35 -0700
Brian Norris <briannorris@chromium.org> wrote:
> On Fri, Sep 25, 2026 at 04:58:14PM +0200, Andreas Kemnade wrote:
> > 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.
>
> 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.
> 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*.
> 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
next prev parent reply other threads:[~2026-09-26 7:00 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 [this message]
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=20260926090026.22b00f57@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