From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 78027C67871 for ; Tue, 25 Oct 2022 00:42:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230262AbiJYAmU (ORCPT ); Mon, 24 Oct 2022 20:42:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34150 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230309AbiJYAmI (ORCPT ); Mon, 24 Oct 2022 20:42:08 -0400 Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B26781C9054 for ; Mon, 24 Oct 2022 16:13:26 -0700 (PDT) Received: by mail-lf1-x12e.google.com with SMTP id g1so19066612lfu.12 for ; Mon, 24 Oct 2022 16:13:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=N++ECBeiYTMrGhdzzlYvKWtcZRGylld/eBk1VfSFo+0=; b=Jb3dJUcj77xb+NVMl3d7F4DKDlJf9tqwDpl7Xk1CzibXBGhUajRZ+DnWG+TJlG/TnW DkMeADFDKCGWeMHhH4H8KSku8hvHXNMJ0HlnDBe6GX/lhngtZqXN1wUC+fW42a1nJxeE efabcSBwNuQI7669JcRJzn0CmSoqz1pK59H7Y= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=N++ECBeiYTMrGhdzzlYvKWtcZRGylld/eBk1VfSFo+0=; b=fPkF0HSGT1DPEaRzgCvKYjwmt6nq21PpVYiiJYxBIeAd7/b974tpBHg+8thIBzQxfa A2nAcA3h3WSXjun6OtabTBZObSs7ScdG4N0S6sVnjuRgWbo9bGXJCjHPL/4Zdp9Vkcun xh7DQmHDO6XSaZe5/Eo1DZbvohwT2m3bWRwYyR4XEIHrcGgrvu2DQ8TV7jAGceqY1XZo wlFP0bH9F80+aRgP+bd82U8bkzmtBFGnR6tt6k/NhoJkHVl8JkavrJWt95/ZZv5gRLbD yZV335gaQl89yMLGuirSs2vrxfdqgif5/+yEjyKl5xpxM4LZDS1mjFrGdlBTc2DE0Bim kY7Q== X-Gm-Message-State: ACrzQf0GI9pL5qFM6lwCToeYP6KTD6gpDzbPbM3as80LOdg0CbxBlHa/ MdfehN1tDTR8ucTwk4dJbPZ5zebyoCVNqPJHtgPEoA== X-Google-Smtp-Source: AMsMyM4zgnkTMjwuPQychO5/KeczfWRL6z5D7QwOTlvV0HoDnDHmmJJoSpbO/Td0JYGontrEUP3ONUHVi4cb5C+4yLM= X-Received: by 2002:a05:6512:104e:b0:4a2:6bd2:4db5 with SMTP id c14-20020a056512104e00b004a26bd24db5mr13284277lfb.52.1666653205078; Mon, 24 Oct 2022 16:13:25 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nathan Hebert Date: Mon, 24 Oct 2022 16:13:12 -0700 Message-ID: Subject: Re: [PULL V2]: qcom: SC7180 and SC7280 venus firmware updates To: Dmitry Baryshkov Cc: linux-firmware@kernel.org, Rob Clark , linux-arm-msm@vger.kernel.org, Bjorn Andersson , Fritz Koenig , Vikash Garodia Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Thu, Oct 20, 2022 at 11:02 AM Dmitry Baryshkov wrote: > > On Thu, 20 Oct 2022 at 20:08, Nathan Hebert wrote: > > > > The following changes since commit 48407ffd7adb9511701547068b1e6f0956bd1c94: > > > > cnm: update chips&media wave521c firmware. (2022-10-17 10:20:43 -0400) > > > > are available in the Git repository at: > > > > https://github.com/nathan-google/linux-firmware.git > > update_sc7180_and_sc7280_firmwares_v2 > > > > for you to fetch changes up to 054271e4164b6b4c069a3aaaeb9bfcde8c850339: > > > > qcom: update venus firmware files for VPU-2.0 (2022-10-20 09:37:35 -0700) > > > > ---------------------------------------------------------------- > > Nathan Hebert (3): > > qcom: update venus firmware files for v5.4 > > qcom: remove split SC7280 venus firmware images > > qcom: update venus firmware files for VPU-2.0 > > > > WHENCE | 17 ++--------------- > > qcom/venus-5.4/venus.b00 | Bin 212 -> 212 bytes > > qcom/venus-5.4/venus.b01 | Bin 6808 -> 6808 bytes > > qcom/venus-5.4/venus.b02 | Bin 873596 -> 875020 bytes > > qcom/venus-5.4/venus.b03 | Bin 33792 -> 33896 bytes > > qcom/venus-5.4/venus.mbn | Bin 919708 -> 921236 bytes > > qcom/venus-5.4/venus.mdt | Bin 7020 -> 7020 bytes > > qcom/vpu-2.0/venus.b00 | Bin 692 -> 0 bytes > > qcom/vpu-2.0/venus.b01 | Bin 7376 -> 0 bytes > > qcom/vpu-2.0/venus.b02 | Bin 300 -> 0 bytes > > qcom/vpu-2.0/venus.b03 | Bin 20 -> 0 bytes > > qcom/vpu-2.0/venus.b04 | Bin 20 -> 0 bytes > > qcom/vpu-2.0/venus.b05 | Bin 20 -> 0 bytes > > qcom/vpu-2.0/venus.b06 | Bin 20 -> 0 bytes > > qcom/vpu-2.0/venus.b07 | Bin 24 -> 0 bytes > > qcom/vpu-2.0/venus.b08 | Bin 16 -> 0 bytes > > qcom/vpu-2.0/venus.b09 | Bin 939184 -> 0 bytes > > qcom/vpu-2.0/venus.b10 | Bin 42976 -> 0 bytes > > qcom/vpu-2.0/venus.b19 | 1 - > > qcom/vpu-2.0/venus.mbn | Bin 2031188 -> 2031620 bytes > > qcom/vpu-2.0/venus.mdt | Bin 8068 -> 0 bytes > > 21 files changed, 2 insertions(+), 16 deletions(-) > > delete mode 100644 qcom/vpu-2.0/venus.b00 > > delete mode 100644 qcom/vpu-2.0/venus.b01 > > delete mode 100644 qcom/vpu-2.0/venus.b02 > > delete mode 100644 qcom/vpu-2.0/venus.b03 > > delete mode 100644 qcom/vpu-2.0/venus.b04 > > delete mode 100644 qcom/vpu-2.0/venus.b05 > > delete mode 100644 qcom/vpu-2.0/venus.b06 > > delete mode 100644 qcom/vpu-2.0/venus.b07 > > delete mode 100644 qcom/vpu-2.0/venus.b08 > > delete mode 100644 qcom/vpu-2.0/venus.b09 > > delete mode 100644 qcom/vpu-2.0/venus.b10 > > delete mode 100644 qcom/vpu-2.0/venus.b19 > > delete mode 100644 qcom/vpu-2.0/venus.mdt > > As I wrote in another email thread, it might be better to drop split > files, add only venus.mbn and then use Link: lines to create venus.mdt > -> venus.mbn symlinks. Thanks for the feedback. There was some concern from Vikash at Qualcomm about making a change to the venus-5.4 firmware to drop the split files. Vikash, are you able to comment about whether or not it is a concern to replace the venus.mdt and split files with a symbolic link to venus.mdn for the venus-5.4 files? I tested the suggested approach on ChromeOS with kernels based on 5.4 and 5.15 and did not see any issues. This is a holiday week, so his response may be slow. > > -- > With best wishes > Dmitry