Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure declarative boot order doesn't influence initrd flash script #255

Merged
merged 4 commits into from
Nov 22, 2024

Conversation

jmbaur
Copy link
Contributor

@jmbaur jmbaur commented Nov 21, 2024

Description of changes

Including the DTBO used for configuring the boot order in the initrd flash script means that the temporary edk2 build used only for flashing has the possibility of booting from something other than the kernel/initrd meant for flashing. Excluding this DTBO when performing the initrd flash method means that this is no longer possible.

Testing

Tested on an xavier-agx-devkit that was previously netbooting when attempting to use the initrd flash script.

Including the DTBO used for configuring the boot order in the initrd
flash script means that the temporary edk2 build used only for flashing
has the possibility of booting from something other than the
kernel/initrd meant for flashing. Excluding this DTBO when performing
the initrd flash method means that this is no longer possible.
The `initrd=` kernel command-line argument is used by the EFI stub to
determine where to pickup the initrd from an ESP. Since in the RCM boot
case there is no ESP, it doesn't make sense to specify it here.
@danielfullmer danielfullmer merged commit abfe7f4 into anduril:master Nov 22, 2024
1 check failed
@jmbaur jmbaur deleted the initrd-flash-boot-order-fixes branch November 22, 2024 22:21
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.

2 participants