Received: by 2002:a05:6358:700f:b0:131:369:b2a3 with SMTP id 15csp3355132rwo; Fri, 4 Aug 2023 03:45:29 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFOyQGveiiZBewqhQ+4YvXc8G8ivyhgQFyDNFVGq1jiIVOUsuH6LPCtGohXoc5hJMp8XdtI X-Received: by 2002:a2e:780b:0:b0:2b6:e536:a2a3 with SMTP id t11-20020a2e780b000000b002b6e536a2a3mr1192643ljc.19.1691145929481; Fri, 04 Aug 2023 03:45:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1691145929; cv=none; d=google.com; s=arc-20160816; b=nwpv/FdkqbdYHog2Hx1PHrpnSEVkRjgbdnQ6wmroB1J3dOZO1IgOI5W7vuZ3WD3u4J FxBMoEdiij8oMwW1grjDnvfj+eoynmTEHB3nMVZRNvhDlLKnaV34ZcORRI3m8VKRJj0C QkhZE9pdTx6/dacyBLWgJCCFpNJ/7OTX98Z1wwcTHMckr3ESJzGR3BufAjw6SCGYwilK m0TAV0UULEvNrd9e3n0d3Ha/hAJbC1M6kq7l1OmcnlXlYex1n6muCrckwl5VwYAfc/sw EVJlEeur3fw4qBDL76zn1VUoTe5q6xjqfHs9yKkVuPwQVt1eCVVFultHYRRht0XVhySq jFxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:reply-to :from:references:cc:to:content-language:subject:user-agent :mime-version:date:message-id; bh=8sf6I8tY0JEd2BBPIqDrRw3VWrV0++vZ4wFitDORsPE=; fh=WoDHcyJo7o6/w97SFIcQJA29RBvsSPJn4yQk4LnT6TQ=; b=erUCw4OKclvZYyyhG2R1dcmsI2pwTZAazUXbplQCpyben6LuPSUw1O2+BcthiWfSOd uEwn0HfAzV+MeULonh1l3+V0Sr9YV/FaDRr+8iJrKMDfhhH+Qxidag3mQX5Wq3gp0htc J3fpBYiZ0dccfHdZojTOO4um1M8zIa6vQeZS5TU5mL89xxnn1H9JvONwjaW3YcP14gd5 Jrke5Ur32KfGUoI8X7a41cGQ9B5Hu04aguYuRNy+W0v/ZgGJRzasR9NDmP0+pBf220co fyvojoMZwvcUF3wPTvaH0gZZN1JgPNv0ANXiUFh/OubTmBmQb0K10n/O5LkxsKKIQdZb mVoA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id qx17-20020a170906fcd100b0099bbff8672fsi1492186ejb.696.2023.08.04.03.45.04; Fri, 04 Aug 2023 03:45:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-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; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231467AbjHDKcM (ORCPT + 99 others); Fri, 4 Aug 2023 06:32:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42350 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231411AbjHDKcD (ORCPT ); Fri, 4 Aug 2023 06:32:03 -0400 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1A64430F6; Fri, 4 Aug 2023 03:32:02 -0700 (PDT) Received: from [2a02:8108:8980:2478:8cde:aa2c:f324:937e]; authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1qRs68-0000ML-HP; Fri, 04 Aug 2023 12:31:56 +0200 Message-ID: Date: Fri, 4 Aug 2023 12:31:55 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C Content-Language: en-US, de-DE To: Max Chou , Linux regressions mailing list , "marcel@holtmann.org" Cc: "johan.hedberg@gmail.com" , "luiz.dentz@gmail.com" , "linux-bluetooth@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "alex_lu@realsil.com.cn" , Hilda Wu , Karen Hsu , KidmanLee , "juerg.haefliger@canonical.com" , "vicamo.yang@canonical.com" , "Riley.Kao@dell.com" , Josh Boyer , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni References: <20230804055426.6806-1-max.chou@realtek.com> <202308040950.3749oOuG5031679@rtits1.realtek.com.tw> From: "Linux regression tracking (Thorsten Leemhuis)" Reply-To: Linux regressions mailing list In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1691145122;2c63205b; X-HE-SMSGID: 1qRs68-0000ML-HP X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS 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-bluetooth@vger.kernel.org On 04.08.23 12:15, Max Chou wrote: >> -----Original Message----- >> [CCing the linux-firmware maintainer, the network maintainers, and the >> regressions lists] >> >> On 04.08.23 07:54, max.chou@realtek.com wrote: >>> From: Max Chou >>> >>> In the commit of linux-firmware project, rtl8852cu_fw.bin is updated >>> as FW v2 format[1]. Consider the case that if driver did not be updated fo> >> FW v2 supported[2], it can not use FW v2. >>> >>> By Canonical's suggestion, older driver should be able to load FW v1, >> >> Well, that's not only Canonical suggestion, that is how things are supposed to >> be handled in general. See >> Documentation/driver-api/firmware/firmware-usage-guidelines.rst (alt: >> https://docs.kernel.org/driver-api/firmware/firmware-usage-guidelines.html >> ) for details. >> >> We had a similar situation in March already with a Wifi driver: >> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/c >> ommit/?id=416a66cae796939d7d096988c72c641656c81c5a >> >> Makes me wonder: is there a problem here we should try harder to avoid? >> Especially as the problem in this case would have been simple to predict by >> reading the changelog of the linux-firmware change. To quote from >> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/c >> ommit/?id=55e7448533e7 >> >> ``` >> Note: This firmware patch needs to be used with driver >> "btrtl: Firmware format v2 support". Please update the driver with this commit: >> 9a24ce5e29b15c4c6b0c89c04f9df6ce14addefa >> ``` > > Actually, we thought this note is enough. [...] Yeah, no big deal, error are made and dealt with, and you are working on that. Thx for that. It's just that the episode got got me thinking: It's the second time such error is made within a a few months, hence I wonder if we on the side of the Linux kernel and/or Linux-firmware should change something to ideally prevent this from happening. Ciao, Thorsten