BUP image and UEFI Capsule generation questions #1492
Unanswered
igoropaniuk
asked this question in
Q&A
Replies: 1 comment
-
There's some history to the way this is structured that pre-dates UEFI and capsules. There's also some history to the assumption that the kernel uses a initrd. Going forward, I'd like to get rid of the separate BUP generation and move that into the capsule creation recipes. If you're having problems building/using a kernel without an initrd because a kernel BUP never gets generated, that should probably be fixable in the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been learning recently about how BUP/UEFI capsules are generated in the latest master.
Correct my if I'm wrong:
BUP creation logic is implemented in
classes/image_types_tegra.bbclass
, increate_bup_payload_image()
:This function is defined in CONVERSION_CMD for
bup-payload
image typeCONVERSION_CMD:bup-payload = "create_bup_payload_image ${type}"
, which implies that we should have some image with bup-payload type defined inINITRAMFS_FSTYPES
.Final UEFI capsule is generated by
tegra-uefi-capsule
recipe, which expects BUP blobs to be deployed to$DEPLOY_DIR_IMAGE
in advance.Was there any particular reason why BUP creation is done via
CONVERSION_CMD
and not in a dedicated recipe (like it's currently done for UEFI capsule generation integra-uefi-capsule
recipe)? is there any some sort of update process which requires a running initrd?Beta Was this translation helpful? Give feedback.
All reactions