You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UEFI spec mentions that the client gets the Boot URI and the Optional Boot Parameters from the DHCPOFFER for DHCPv6. I do not see support for the Optional Boot Parameter "BootFile" in edk2/NetworkPkg/HttpBootDxe. Would it be fair to say that you cannot pass boot parameters to the image you download? I would expect the Optional BootFile to be passed to the .efi image as LoadOptions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
The UEFI spec mentions that the client gets the Boot URI and the Optional Boot Parameters from the DHCPOFFER for DHCPv6. I do not see support for the Optional Boot Parameter "BootFile" in
edk2/NetworkPkg/HttpBootDxe
. Would it be fair to say that you cannot pass boot parameters to the image you download? I would expect the Optional BootFile to be passed to the.efi
image asLoadOptions
.https://datatracker.ietf.org/doc/html/rfc5970#section-3.2 also has mention of the Optional BootFile.
Beta Was this translation helpful? Give feedback.
All reactions