All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Wed, 2 Mar 2022 19:50:14 +0200	[thread overview]
Message-ID: <20220302175014.GA14801@w1.fi> (raw)
In-Reply-To: <CA+5PVA5DJmwPqpz8F9iDbJKcF1hDBRLdDT4URgSaiEcjet74Kw@mail.gmail.com>

On Fri, Feb 18, 2022 at 10:55:37AM -0500, Josh Boyer wrote:
> On Thu, Feb 10, 2022 at 5:45 AM Kalle Valo <kvalo@kernel.org> wrote:
> > > On Thu, Dec 23, 2021 at 9:03 AM Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> > >>
> > >>  WHENCE                           |   14 +-
> > >>  ath11k/IPQ6018/hw1.0/Notice.txt  |   48 +-

> > > These Notice files seem problematic.  They're clearly well intended,
> > > but they have language that alludes to an agreement with Atheros and a
> > > confidential nature to some of the files.  Specifically:
> > >
> > > "...your use of these software
> > > components together with the Qualcomm Atheros software (Qualcomm
> > > Atheros software hereinafter referred to as “Software”) is
> > > subject to the terms of your agreement from Qualcomm Atheros."
> > >
> > > Nobody has an opportunity to agree to anything with Atheros when they
> > > consume the files from linux-firmware.  There's also no explicit grant
> > > of redistribution for any of these files.

This is not the license; this is a description of the notice.txt file
containing the notices to cover the 3rd party license requirements for
attribution/notices included in redistribution of those parts.

> > So this file we are discussing is the notice.txt file. In the WHENCE
> > file the actual license for ath11k is:
> >
> > Licence: Redistributable. See LICENSE.QualcommAtheros_ath10k for details

And this is where the license is and this includes license to
redistribute.

> Then is the notice.txt file needed at all?  If a user or distribution
> were to install this firmware, is the expectation that the notice.txt
> file also be installed?

Those 3rd party license might require various notifications to be
included for notification/attribution purposes, so I would expect the
notice.txt file to be redistributed whenever the firmware image is
redistributed.

> > Does that cover your concerns about redistribution?
> 
> Not really.  I understand the logic, but if the binding license for
> the firmware is LICENSE.QualcommAtheros_ath10k but we still need
> notice.txt for some reason, they conflict.  It's ambiguous at best.

Could you please be more specific on where you see a conflict? Maybe
this would be clearer if the WHENCE file would not mark the notice.txt
files with the "License: <file>" lines since these are not the license
for the firmware binary and then there would be a single "License:" line
pointing out the exact license that applies?

Would the following in WHENCE work for you?

Driver: ath11k - Qualcomm Technologies 802.11ax chipset support

File: ath11k/IPQ6018/hw1.0/board-2.bin
...
Version: WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2
Notice: ath11k/IPQ6018/hw1.0/Notice.txt
...
File: ath11k/QCA6390/hw2.0/m3.bin
Version: WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1
Notice: ath11k/QCA6390/hw2.0/Notice.txt

Licence: Redistributable. See LICENSE.QualcommAtheros_ath10k for details


In other words, there would be only a single "License:" line and one
"Notice:" line for each firmware version? The license itself (i.e.,
LICENSE.QualcommAtheros_ath10k) is same for all the versions while the
set of notices (i.e., those notice.txt files) can be different based on
what is included in the particular build.

> > I'm still working on your other comment about notice.txt, will get back
> > on that later.

This part about clearly identifying the files should be clear now, but
it would be good to resolve that part about the notice.txt files in
general before sending out an updated pull request.

-- 
Jouni Malinen                                            PGP id EFC895FA

WARNING: multiple messages have this Message-ID (diff)
From: Jouni Malinen <j@w1.fi>
To: Josh Boyer <jwboyer@kernel.org>
Cc: Kalle Valo <kvalo@kernel.org>,
	"linux-firmware@kernel.org" <linux-firmware@kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PULL] ath11k firmware 20211223
Date: Wed, 2 Mar 2022 19:50:14 +0200	[thread overview]
Message-ID: <20220302175014.GA14801@w1.fi> (raw)
In-Reply-To: <CA+5PVA5DJmwPqpz8F9iDbJKcF1hDBRLdDT4URgSaiEcjet74Kw@mail.gmail.com>

On Fri, Feb 18, 2022 at 10:55:37AM -0500, Josh Boyer wrote:
> On Thu, Feb 10, 2022 at 5:45 AM Kalle Valo <kvalo@kernel.org> wrote:
> > > On Thu, Dec 23, 2021 at 9:03 AM Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> > >>
> > >>  WHENCE                           |   14 +-
> > >>  ath11k/IPQ6018/hw1.0/Notice.txt  |   48 +-

> > > These Notice files seem problematic.  They're clearly well intended,
> > > but they have language that alludes to an agreement with Atheros and a
> > > confidential nature to some of the files.  Specifically:
> > >
> > > "...your use of these software
> > > components together with the Qualcomm Atheros software (Qualcomm
> > > Atheros software hereinafter referred to as “Software”) is
> > > subject to the terms of your agreement from Qualcomm Atheros."
> > >
> > > Nobody has an opportunity to agree to anything with Atheros when they
> > > consume the files from linux-firmware.  There's also no explicit grant
> > > of redistribution for any of these files.

This is not the license; this is a description of the notice.txt file
containing the notices to cover the 3rd party license requirements for
attribution/notices included in redistribution of those parts.

> > So this file we are discussing is the notice.txt file. In the WHENCE
> > file the actual license for ath11k is:
> >
> > Licence: Redistributable. See LICENSE.QualcommAtheros_ath10k for details

And this is where the license is and this includes license to
redistribute.

> Then is the notice.txt file needed at all?  If a user or distribution
> were to install this firmware, is the expectation that the notice.txt
> file also be installed?

Those 3rd party license might require various notifications to be
included for notification/attribution purposes, so I would expect the
notice.txt file to be redistributed whenever the firmware image is
redistributed.

> > Does that cover your concerns about redistribution?
> 
> Not really.  I understand the logic, but if the binding license for
> the firmware is LICENSE.QualcommAtheros_ath10k but we still need
> notice.txt for some reason, they conflict.  It's ambiguous at best.

Could you please be more specific on where you see a conflict? Maybe
this would be clearer if the WHENCE file would not mark the notice.txt
files with the "License: <file>" lines since these are not the license
for the firmware binary and then there would be a single "License:" line
pointing out the exact license that applies?

Would the following in WHENCE work for you?

Driver: ath11k - Qualcomm Technologies 802.11ax chipset support

File: ath11k/IPQ6018/hw1.0/board-2.bin
...
Version: WLAN.HK.2.1.0.1-01238-QCAHKSWPL_SILICONZ-2
Notice: ath11k/IPQ6018/hw1.0/Notice.txt
...
File: ath11k/QCA6390/hw2.0/m3.bin
Version: WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1
Notice: ath11k/QCA6390/hw2.0/Notice.txt

Licence: Redistributable. See LICENSE.QualcommAtheros_ath10k for details


In other words, there would be only a single "License:" line and one
"Notice:" line for each firmware version? The license itself (i.e.,
LICENSE.QualcommAtheros_ath10k) is same for all the versions while the
set of notices (i.e., those notice.txt files) can be different based on
what is included in the particular build.

> > I'm still working on your other comment about notice.txt, will get back
> > on that later.

This part about clearly identifying the files should be clear now, but
it would be good to resolve that part about the notice.txt files in
general before sending out an updated pull request.

-- 
Jouni Malinen                                            PGP id EFC895FA

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2022-03-02 17:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 14:03 [PULL] ath11k firmware 20211223 Kalle Valo
2021-12-23 14:03 ` Kalle Valo
2021-12-23 17:24 ` Mark Herbert
2021-12-29 13:41 ` Josh Boyer
2021-12-29 13:41   ` Josh Boyer
2022-01-10 15:19   ` Kalle Valo
2022-01-10 15:19     ` Kalle Valo
2022-02-10 10:45   ` Kalle Valo
2022-02-10 10:45     ` Kalle Valo
2022-02-18 15:55     ` Josh Boyer
2022-02-18 15:55       ` Josh Boyer
2022-03-02 17:50       ` Jouni Malinen [this message]
2022-03-02 17:50         ` Jouni Malinen
2022-03-04 13:04         ` Josh Boyer
2022-03-04 13:04           ` Josh Boyer
2022-03-04 16:14           ` Jouni Malinen
2022-03-04 16:14             ` Jouni Malinen
2022-03-23  8:06             ` Takashi Iwai
2022-03-23  8:06               ` Takashi Iwai
2022-04-13  8:26               ` Kalle Valo
2022-04-13  8:26                 ` Kalle Valo
2022-04-13  8:40                 ` Takashi Iwai
2022-04-13  8:40                   ` Takashi Iwai
2022-02-18 15:00 ` Sven Eckelmann
2022-02-18 15:00   ` Sven Eckelmann
2022-04-13  8:28   ` Kalle Valo
2022-04-13  8:28     ` Kalle Valo

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=20220302175014.GA14801@w1.fi \
    --to=j@w1.fi \
    --cc=ath11k@lists.infradead.org \
    --cc=jwboyer@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=linux-firmware@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.