LAVA: route boot to fastboot_fastrpc to preserve firmware archive layout#306
Open
quic-mtharu wants to merge 1 commit intoqualcomm:developmentfrom
Open
LAVA: route boot to fastboot_fastrpc to preserve firmware archive layout#306quic-mtharu wants to merge 1 commit intoqualcomm:developmentfrom
quic-mtharu wants to merge 1 commit intoqualcomm:developmentfrom
Conversation
Update LAVA job invocation to set BOOT_METHOD=fastboot_fastrpc instead of BOOT_METHOD=fastboot. The existing fastboot template path combines firmware archives using stream concatenation (cat), which does not preserve a unified filesystem layout and can break symlink/path resolution (e.g., /lib -> /usr/lib and firmware files in a separate archive). The fastboot_fastrpc boot method points jobs to a dedicated template that merges firmware archives via extract+repack, preserving the directory hierarchy and symlinks required for early boot firmware loads. This change is scoped only to FastRPC job flow and does not impact the default fastboot template behavior. Signed-off-by: Tharun Kumar Merugu <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the FastRPC LAVA job execution path to export:
export BOOT_METHOD=fastboot_fastrpcinstead of:
export BOOT_METHOD=fastbootBackground / Problem
We observed FastRPC LAVA failures during post‑processing and early boot when firmware is supplied as multiple archives and then combined using simple concatenation (
cat) in the existing fastboot template flow.Concatenation does not merge filesystem trees or correctly preserve cross-archive symlink/path semantics. In our case,
/libis defined as a symlink to/usr/libin one archive, while firmware content is provided in another archive. When the archives are concatenated,/lib/firmwaredoes not resolve correctly during early boot, causing firmware load failures and driver init issues.Change
FastRPC jobs now use the
fastboot_fastrpcboot method, which routes to a dedicated template (templates/boot/fastboot_fastrpc.jinja2) that merges firmware archives using extract → merge → repack. This preserves:/lib -> /usr/lib)/lib/firmwareresolutionScope / Impact
fastbootboot method behaviorBOOT_METHOD=fastbootTest Plan
fastboot_fastrpcflow: Job LAVA | Scheduler | Jobs | 41841Notes
This PR only switches the boot method selector. The functional change (archive merge logic) lives in the dedicated
fastboot_fastrpctemplate.