Skip to content

lemans: fix linux-firmware sparse-checkout on git 2.34 - #2

Open
bibekpatro wants to merge 3 commits into
ldts:mainfrom
bibekpatro:fix/linux-firmware-sparse-checkout
Open

lemans: fix linux-firmware sparse-checkout on git 2.34#2
bibekpatro wants to merge 3 commits into
ldts:mainfrom
bibekpatro:fix/linux-firmware-sparse-checkout

Conversation

@bibekpatro

Copy link
Copy Markdown

git 2.34 has a bug where combining --filter=blob:none and --sparse in a single git clone fails to create .git/info/ before attempting to initialize sparse-checkout, resulting in:

fatal: could not open '.git/info/sparse-checkout' for writing:
No such file or directory

Fix by dropping --sparse from the clone invocation and running git sparse-checkout init as a separate step after the clone completes, at which point .git/info/ exists.

Change-Id: Ic8d61bf54b87b453e836c57cce73734d5b814c41

git 2.34 has a bug where combining --filter=blob:none and --sparse in
a single git clone fails to create .git/info/ before attempting to
initialize sparse-checkout, resulting in:

  fatal: could not open '.git/info/sparse-checkout' for writing:
  No such file or directory

Fix by dropping --sparse from the clone invocation and running
git sparse-checkout init as a separate step after the clone
completes, at which point .git/info/ exists.

Signed-off-by: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
@bibekpatro
bibekpatro force-pushed the fix/linux-firmware-sparse-checkout branch from bf8b4c7 to 5a9a34b Compare August 20, 2026 11:08
The EFI stub rejects the kernel with:

  EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary

This happens because the kernel is built with CONFIG_ARM64_4K_PAGES
which only guarantees 4K alignment, but the EFI stub requires the
kernel to be placed on a 64K boundary.

Switch to CONFIG_ARM64_64K_PAGES so the kernel image alignment
satisfies the EFI stub requirement.

Signed-off-by: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
The kernel's QCOM SCM driver calls __get_convention() unconditionally
at early boot to probe the SMC calling convention. It issues SMC
0x72000602 (SVC_INFO / IS_CALL_AVAIL) which OP-TEE does not handle,
causing an 'Unknown SMC' error and leaving the kernel hung waiting
for a response that never comes.

Disable CONFIG_QCOM_SCM since this lemans build targets OP-TEE, not
QSEE/TZ, and there is no qcom,scm firmware node in the device tree.

Signed-off-by: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant