Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp3576161pxp; Wed, 23 Mar 2022 01:12:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy7M4s0AVMrOdwor2JbaB5Hs/oXhScz5dK2dG1DIb8uiqqvJ4xAGIivBIeziSKfx8NNr6x9 X-Received: by 2002:a17:90a:d681:b0:1be:e3e5:3e6e with SMTP id x1-20020a17090ad68100b001bee3e53e6emr9899281pju.122.1648023120362; Wed, 23 Mar 2022 01:12:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648023120; cv=none; d=google.com; s=arc-20160816; b=MVXrbQQH/tRXs4LU/Fi1D6eH+YrYOmesuyTjL9q79YZETg2q0ZRCJTcoPeVASA788l g73WKslGMP7qz9dlsyZfknxK4O4Ow895CXtF5j1yaL1CHhnnDYuX0109ZL2763W4hlgC G0P1I2X2rMJjEIWXFPLjq7vlVcnQSDxbUBgNpcEwM7IRn9/iQ0JcBlpcCYQaWxSF1OCM VdAfsccAsBqb6xFwOZ60iBSesDIUPVMsiAs+dIfl2uY5bkD6JWtuVxqjNRtLW6Xte01E 1IAyuqWxq6FCb5RK1qBHVS7rXdrtcEitxZiZQ2E/oJDtDYE8ofyIFE9WeRljB4Dky6Jh lOBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date:dkim-signature:dkim-signature; bh=fVc1r9WWP/81nZVxNXVVFWksf7u2PARCyEh4wB1yqlQ=; b=ujHbDSvgxjT/Ht4ciJukHwTOu/dpnn2u5SNczDqhGqWVKUXo5yaEtpAqRr1xfMvAYP DwkmNJV/r9JuCt1sfJdnmbf2CylHXxymbW6xo6Etz0RrvexCYlq94N0+2/5M+SiljPll SKspKTI4ZpBgZcNu9j4KpU5wfV7ymFqcws1qygfEKnAkMbS+0YZQwfsm8p3D7rOTr02+ VBKQpYLWU1Hdne+4Rq778VRhyK385kYwGrmCSvJxnRsTUNlyLclzVkiRKco9lhpECtCY A5X39fKVLJQK05GCJhh0lwFpgu+d7KQLP25T1WSAQ+eRARQj2AfWcmwWofUxFAhNDf+P aF6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b="EUEK/bdY"; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id s1-20020a17090302c100b00153b2d16460si14821237plk.104.2022.03.23.01.11.45; Wed, 23 Mar 2022 01:12:00 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b="EUEK/bdY"; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=suse.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233488AbiCWIJu (ORCPT + 70 others); Wed, 23 Mar 2022 04:09:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40208 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233418AbiCWIIO (ORCPT ); Wed, 23 Mar 2022 04:08:14 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5C38474871 for ; Wed, 23 Mar 2022 01:06:45 -0700 (PDT) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out1.suse.de (Postfix) with ESMTP id EA8E6210F4; Wed, 23 Mar 2022 08:06:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1648022803; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fVc1r9WWP/81nZVxNXVVFWksf7u2PARCyEh4wB1yqlQ=; b=EUEK/bdYvFT5KqU9KZF5vHdcQ8zKAr3c8miuojG7TF/PiIWZ/rOPmbVlgtd3e7wQbvyw7D rhra0ywEAaaA3ULFWvEo/E2cyQKRMQSeDQ7zKwb3Tf417NkEaWl5g5/i5rh+gH+TSVlUsc Vluiz7xLtaG9aABcfctv6dj1lqaV34I= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1648022803; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fVc1r9WWP/81nZVxNXVVFWksf7u2PARCyEh4wB1yqlQ=; b=eBYrBA1C6MhLmQSW2zFSxQHgsSTzVwC/8EKQ9psYwslBkeKvSgbajse7yZoTISOFoe5F+L 2Qr4ETO/2CLhk0Cw== Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42]) by relay2.suse.de (Postfix) with ESMTP id DE944A3B88; Wed, 23 Mar 2022 08:06:43 +0000 (UTC) Date: Wed, 23 Mar 2022 09:06:43 +0100 Message-ID: From: Takashi Iwai To: Jouni Malinen Cc: Josh Boyer , Kalle Valo , "linux-firmware@kernel.org" , "linux-wireless@vger.kernel.org" , "ath11k@lists.infradead.org" Subject: Re: [PULL] ath11k firmware 20211223 In-Reply-To: <20220304161430.GA430462@w1.fi> References: <87ee4brodv.fsf@kernel.org> <20220302175014.GA14801@w1.fi> <20220304161430.GA430462@w1.fi> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 04 Mar 2022 17:14:30 +0100, Jouni Malinen wrote: > > On Fri, Mar 04, 2022 at 08:04:26AM -0500, Josh Boyer wrote: > > On Wed, Mar 2, 2022 at 12:50 PM Jouni Malinen 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. The problem of "File:" is that it's more or less intended to be installed as the firmware files themselves, i.e. they are installed in /lib/firmware/* that can be loaded to the kernel. Putting such a random (document) file there makes me a bit nervous. We may introduce another tag to list up misc document files (e.g. "Doc:" or whatever)? Distros can pick up them and put to the appropriate places in the package, too. thanks, Takashi