Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp3373929pxv; Mon, 28 Jun 2021 03:13:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQCVl5ZLm+F7V5QUY94XfPw5+h/6XICoOvQyBWNcYfLi1buKmxHG1tsNEzIdDqYK5hr5Ds X-Received: by 2002:a92:d6c6:: with SMTP id z6mr16644817ilp.89.1624875197351; Mon, 28 Jun 2021 03:13:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624875197; cv=none; d=google.com; s=arc-20160816; b=BqdidJk7BXeswIEAg9GbzCVIggN0dmupx8NzBl0jlvP0ExnLw31NwsUZmAk8wTzAO4 gJFVmI9oRZr8ql2tCuoRfRu66Ly50oNrYzj06uuvwEMFgOcipvataCls23NfpXt4rpTA Ma9kFia+IGqtMW6Ku/GrWbE5z8A1fzexld8zEUDnKtcc/ESCXlg3zINyowZGWrTkRDPb 1FSIiayyKoyPsn5VXtKLN/j624s+PVJm8gOxHMtUx3GsAVfuGmV43a0v21jpsq2VjvB2 ABNiuGnqS3vYpFB3UosPnpJ00lFHJMyJ1OB5Kxah4MvHLfg+365bVIpeVDeThzlxd2gR uI5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature:dkim-filter; bh=F1zp2PVpeuWNxPIpr0z0pCgsOiu8BSgOJY48QmULL/g=; b=o4klM9f95i3lXTGKZKcDsI806KzYuY5A6ZJwVaCdGpiA0ITDUJHqPpcJacGXu4Oble kgP1CIkYKolng5JPjl41mOt6HcOz24qwhphPyBXd4G1iC9WnGjcTcZ+ZzBkG02lfe/ut ACXtw06nXchF7EyTEsmXhxZ2sNDvlO5sRFGNSRdFKcbfBPlwNzBGXjGFEVW52vIJoI57 0YuwaVu7W2GaryOSIeA1xP5GA4OFOPF5Du5SERfYVf00YGXNVkYObMQ3JjabpRiNtBzl qRAu02LHfPdFk7SdLIo8VZe417npCgzmM+XpEyc3d06lyJ1nzC890ZsdueJpaXHcmkzD iPsA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@broadcom.com header.s=dkimrelay header.b=a0t9svh8; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m2si21148661ilu.120.2021.06.28.03.13.05; Mon, 28 Jun 2021 03:13:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@broadcom.com header.s=dkimrelay header.b=a0t9svh8; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232879AbhF1KOf (ORCPT + 99 others); Mon, 28 Jun 2021 06:14:35 -0400 Received: from saphodev.broadcom.com ([192.19.11.229]:35520 "EHLO relay.smtp-ext.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232520AbhF1KO3 (ORCPT ); Mon, 28 Jun 2021 06:14:29 -0400 Received: from bld-lvn-bcawlan-34.lvn.broadcom.net (bld-lvn-bcawlan-34.lvn.broadcom.net [10.75.138.137]) by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id 365027DBA; Mon, 28 Jun 2021 03:12:03 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com 365027DBA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1624875123; bh=7GV6KFu0g0aVtH9w1qkWYhk+UZVnJoVDXbi4mnUgM8A=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=a0t9svh8UgV3kAvIFMZjZNffcxOes+3AdcHzR64lGDUt3nqfZ6PvQg132ULT7WKMI pEiivpVU0xzcyHds+hTrtVSQGclFkprkY5G6EfQRCzjZGP39BV/vF+3Dacas1d2lwz 6/3Su9Qs1DFX/BXjE9cs55UXff96WHRaSJXOh3OY= Received: from [10.176.68.80] (39y1yf2.dhcp.broadcom.net [10.176.68.80]) by bld-lvn-bcawlan-34.lvn.broadcom.net (Postfix) with ESMTPSA id 857B71874BE; Mon, 28 Jun 2021 03:11:59 -0700 (PDT) Subject: Re: [PATCH] brcmfmac: use separate firmware for 43430 revision 2 To: Kalle Valo , Mikhail Rudenko Cc: Arend van Spriel , Franky Lin , Hante Meuleman , Chi-hsien Lin , Wright Feng , Chung-hsien Hsu , "David S. Miller" , Jakub Kicinski , Dmitry Osipenko , Double Lo , Remi Depommier , Amar Shankar , Saravanan Shanmugham , Frank Kao , linux-wireless@vger.kernel.org, brcm80211-dev-list.pdl@broadcom.com, SHA-cyfmac-dev-list@infineon.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210509233010.2477973-1-mike.rudenko@gmail.com> <87a6oxpsn8.fsf@gmail.com> <87o8bvgqt8.fsf@tynnyri.adurom.net> From: Arend van Spriel Message-ID: Date: Mon, 28 Jun 2021 12:11:57 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <87o8bvgqt8.fsf@tynnyri.adurom.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 6/24/2021 6:39 PM, Kalle Valo wrote: > Mikhail Rudenko writes: > >> On 2021-05-10 at 11:06 MSK, Arend van Spriel wrote: >>> On 5/10/2021 1:30 AM, Mikhail Rudenko wrote: >>>> A separate firmware is needed for Broadcom 43430 revision 2. This >>>> chip can be found in e.g. certain revisions of Ampak AP6212 wireless >>>> IC. Original firmware file from IC vendor is named >>>> 'fw_bcm43436b0.bin', but brcmfmac and also btbcm drivers report chip >>> >>> That is bad naming. There already is a 43436 USB device. >>> >>>> id 43430, so requested firmware file name is >>>> 'brcmfmac43430b0-sdio.bin' in line with other 43430 revisions. >>> >>> As always there is the question about who will be publishing this >>> particular firmware file to linux-firmware. >> >> The above mentioned file can be easily found by web search. Also, the >> corresponding patch for the bluetooth part has just been accepted >> [1]. Is it strictly necessary to have firmware file in linux-firmware in >> order to have this patch accepted? > > This patch is a bit in the gray area. We have a rule that firmware > images should be in linux-firmware, but as the vendor won't submit one > and I assume the license doesn't approve the community submit it either, > there is not really any solution for the firmware problem. At the moment I am not sure which company/division is shipping the 43430 rev 2 or 43436. Having it in linux-firmware is still preferred. > On the other hand some community members have access to the firmware > somehow so this patch is useful to the community, and I think taking an > exception to the rule in this case is justified. So I am inclined > towards applying the patch. As an end-user community members using the device are allowed to use the firmware to run on that device. So I tend to agree with you. > Thoughts? I also have another similar patch in the queue: > > https://patchwork.kernel.org/project/linux-wireless/patch/20210307113550.7720-1-konrad.dybcio@somainline.org/ I will review both and comment/ack them. Regards, Arend