From: Renjiang Han <renjiang.han@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>
Cc: linux-firmware@kernel.org,
"Qiwei Liu (QUIC)" <quic_qiweil@quicinc.com>,
Wangao Wang <wangao.wang@oss.qualcomm.com>,
dikshita.agarwal@oss.qualcomm.com
Subject: Re: update firmware binary for v5.4
Date: Fri, 21 Nov 2025 16:07:53 +0800 [thread overview]
Message-ID: <c075a26e-8544-4b8a-81c0-c2473dc36c98@oss.qualcomm.com> (raw)
In-Reply-To: <vh7nnjywovzr7oeaou3uphfhzc7sxry3n3vg3miuj7ydtelu5t@hvylaofyuhbc>
On 11/21/2025 6:24 AM, Dmitry Baryshkov wrote:
> Which ProgramHeader is it? I don't see any alignment issues with the
> 0059 firmware.
>
> $ strings /lib/firmware/qcom/venus-5.4/venus.mbn | grep QC_IMAGE_VERSION
> QC_IMAGE_VERSION_STRING=VIDEO.VE.5.4-00059-PROD-1
>
> $ readelf -l /lib/firmware/qcom/venus-5.4/venus.mbn
>
> Elf file type is EXEC (Executable file)
> Entry point 0xf500000
> There are 5 program headers, starting at offset 52
>
> Program Headers:
> Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
> NULL 0x000000 0x00000000 0x00000000 0x000d4 0x00000 0
> NULL 0x001000 0x0fa00000 0x0fa00000 0x01a98 0x02000 0x1000
> LOAD 0x003000 0x00000000 0x0f500000 0xd5de0 0xd5de0 R E 0x100000
> LOAD 0x0d8de0 0x00100000 0x0f600000 0x08468 0x3f4000 RW 0x100000
> LOAD 0x0e1248 0x004ff000 0x0f9ff000 0x00020 0x00020 RW 0x4
>
> -- With best wishes Dmitry
ELF spec: (Offset % Alignment) must equal (Virtual Address % Alignment).
0x3000 % 0x100000 != 0x00000000 % 0x10000
0x0d8de0 % 0x100000 != 0x00100000 % 0x100000
Therefore, the Program Header alignment in this file does not conform to
the ELF specification.
--
Best regards,
Renjiang Han
next prev parent reply other threads:[~2025-11-21 8:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 9:39 update firmware binary for v5.4 Renjiang Han
2025-11-19 11:25 ` Dmitry Baryshkov
2025-11-19 14:27 ` Vikash Garodia
2025-11-19 14:52 ` Dmitry Baryshkov
2025-11-19 16:19 ` Vikash Garodia
2025-11-19 16:40 ` Dmitry Baryshkov
2025-11-19 17:13 ` Vikash Garodia
2025-11-20 1:03 ` Dmitry Baryshkov
2025-11-20 10:15 ` Vikash Garodia
2025-11-20 22:24 ` Dmitry Baryshkov
2025-11-21 8:07 ` Renjiang Han [this message]
2025-11-20 10:28 ` Renjiang Han
2025-11-21 2:50 ` Wangao Wang
2025-11-21 3:57 ` Renjiang Han
2025-11-21 9:47 ` Vikash Garodia
2025-11-21 11:55 ` Dmitry Baryshkov
2025-12-09 2:18 ` Renjiang Han
-- strict thread matches above, loose matches on Subject: below --
2025-11-21 4:11 Renjiang Han
2025-11-23 14:11 ` Dmitry Baryshkov
2025-11-24 2:15 ` Renjiang Han
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=c075a26e-8544-4b8a-81c0-c2473dc36c98@oss.qualcomm.com \
--to=renjiang.han@oss.qualcomm.com \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-firmware@kernel.org \
--cc=quic_qiweil@quicinc.com \
--cc=vikash.garodia@oss.qualcomm.com \
--cc=wangao.wang@oss.qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.