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: Fri, 4 Mar 2022 18:14:30 +0200	[thread overview]
Message-ID: <20220304161430.GA430462@w1.fi> (raw)
In-Reply-To: <CA+5PVA6R6F=VqAZRf=xDwGcC+cpqLY1kStkoHck53XiLURVyaw@mail.gmail.com>

On Fri, Mar 04, 2022 at 08:04:26AM -0500, Josh Boyer wrote:
> On Wed, Mar 2, 2022 at 12:50 PM Jouni Malinen <j@w1.fi> wrote:
> > 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
> 
> We'd have to teach copy-firmware.sh what to do with a "Notice:" key.
> Is there a reason "File:" wouldn't work?  The intention is to install
> the notices alongside the binaries, so that would accomplish it.

Yeah, that sounds reasonable to me. From copying/installing/distribution
view point, these can really be handled in the exact same way as the
actual firmware binaries in practice.

> > 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.
> 
> Yes, that would help.  Would you be able to adjust the existing
> entries for ath firmware in the same way?

Yes, I'll work with Kalle to update the existing ath* WLAN cases.

> > > > 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.
> 
> Given these were merged in the past, perhaps I'm being overly
> pedantic.  If we can mark them as Files or Notices instead of
> Licenses, I won't hold it up.  It leaves me slightly confused why
> attribution files need to reference agreements with Qualcomm, splatter
> Confidential and Proprietary throughout the file, and reference
> COPYING and README in reference to GPLv2 when the BSD license was
> clearly chosen.  Perhaps that could be cleaned up in the future.

Thanks. We'll remove most of the unnecessary information from the new
notice.txt files and that should get rid of many of the potentially
confusing parts. If that cleanup leaves something confusing in place,
we are open to cleaning these up further in followup patches, but it
would be nice to be able to get the updated versions into
linux-firmware.git without much more additional delay and yes, this
would be with the File: instead of Licence: entries for the notice.txt
files.

-- 
Jouni Malinen                                            PGP id EFC895FA

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

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: Fri, 4 Mar 2022 18:14:30 +0200	[thread overview]
Message-ID: <20220304161430.GA430462@w1.fi> (raw)
In-Reply-To: <CA+5PVA6R6F=VqAZRf=xDwGcC+cpqLY1kStkoHck53XiLURVyaw@mail.gmail.com>

On Fri, Mar 04, 2022 at 08:04:26AM -0500, Josh Boyer wrote:
> On Wed, Mar 2, 2022 at 12:50 PM Jouni Malinen <j@w1.fi> wrote:
> > 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
> 
> We'd have to teach copy-firmware.sh what to do with a "Notice:" key.
> Is there a reason "File:" wouldn't work?  The intention is to install
> the notices alongside the binaries, so that would accomplish it.

Yeah, that sounds reasonable to me. From copying/installing/distribution
view point, these can really be handled in the exact same way as the
actual firmware binaries in practice.

> > 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.
> 
> Yes, that would help.  Would you be able to adjust the existing
> entries for ath firmware in the same way?

Yes, I'll work with Kalle to update the existing ath* WLAN cases.

> > > > 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.
> 
> Given these were merged in the past, perhaps I'm being overly
> pedantic.  If we can mark them as Files or Notices instead of
> Licenses, I won't hold it up.  It leaves me slightly confused why
> attribution files need to reference agreements with Qualcomm, splatter
> Confidential and Proprietary throughout the file, and reference
> COPYING and README in reference to GPLv2 when the BSD license was
> clearly chosen.  Perhaps that could be cleaned up in the future.

Thanks. We'll remove most of the unnecessary information from the new
notice.txt files and that should get rid of many of the potentially
confusing parts. If that cleanup leaves something confusing in place,
we are open to cleaning these up further in followup patches, but it
would be nice to be able to get the updated versions into
linux-firmware.git without much more additional delay and yes, this
would be with the File: instead of Licence: entries for the notice.txt
files.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2022-03-04 16:20 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
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 [this message]
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=20220304161430.GA430462@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.