linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys.f@collabora.com>
To: linux-firmware@kernel.org
Cc: Nathan Hebert <nhebert@chromium.org>
Subject: pull request: add back missing symlink to Qualcomm firmware file
Date: Sat, 21 Jan 2023 08:23:49 +0200	[thread overview]
Message-ID: <5dc7081a8b793baf08f20df6b641a86a80c9e15c.camel@collabora.com> (raw)

Add missing symlink required for Qualcomm SC7180.
As stated in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/qcom/venus-5.4?id=ad9fdba01fd2c909ea7962844211e25aa276e705
likely by mistake file got deleted, instead of replaced by symlink.

It results SC7180 failing to load firmware with following message:

1679 20:43:46.474154  <4>[   18.381820] qcom-venus aa00000.video-codec:
Direct firmware load for qcom/venus-5.4/venus.mdt failed with error -2

After fixing it device booting without error.


The following changes since commit
7e4f0eda76d58024f78ac68d4ffd6f87d63a3a29:

  Merge https://github.com/pkshih/linux-firmware (2023-01-17 08:00:15 -
0500)

are available in the Git repository at:

  https://github.com/nuclearcat/linux-firmware 

for you to fetch changes up to
a02f1168becbaacbae82a7002ff489c137f9b8b4:

  qcom: Fix symlink from venus-5.4/venus.mdt to venus.mbn (2023-01-20
14:18:17 +0200)

----------------------------------------------------------------
Denys Fedoryshchenko (1):
      qcom: Fix symlink from venus-5.4/venus.mdt to venus.mbn

 qcom/venus-5.4/venus.mdt | 1 +
 1 file changed, 1 insertion(+)
 create mode 120000 qcom/venus-5.4/venus.mdt


Thank you!


             reply	other threads:[~2023-01-21  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  6:23 Denys Fedoryshchenko [this message]
2023-01-23 18:06 ` pull request: add back missing symlink to Qualcomm firmware file Nathan Hebert
2023-01-23 18:28   ` Denys Fedoryshchenko

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=5dc7081a8b793baf08f20df6b641a86a80c9e15c.camel@collabora.com \
    --to=denys.f@collabora.com \
    --cc=linux-firmware@kernel.org \
    --cc=nhebert@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).