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
It would be nice to configure UEFI network booting in a MAC address independent way.
That would allow us to have a golden image and use it in any other pi. Currently this cannot be done because the boot option seems to be associated with the MAC address, so it cannot be used in a different pi.
The text was updated successfully, but these errors were encountered:
There is some support for this in UEFI Spec and TianoCore
The current language allows for HW location-independent boot options for USB, HDD, or URI boot options.. This allows describing "boot from USB key" for example regardless of where the disk is located (which USB port, which results in inclusion of PCI/USB DP nodes in the full DevicePath for instance). Similarly for Boot from URI(), a full device path will include the MAC address (and PCI nodes if the NIC is on a PCI device), while a short-form only includes the "Uri()" DP node:
The boot manager must also support booting from a short-form device path that starts with the first element being a URI Device Path (see Table 83). When the boot manager attempts to boot a short-form URI Device Path, it could attempt to connect any device which will produce a device path protocol including a URI device path node until it matches a device, or fail to match any device. The boot manager will enumerate all LoadFile protocol instances, and invoke LoadFile protocol with FilePath set to the short-form device path during the matching process.
Some experiments are needed to figure out how to construct the proper Boot#### option with the short-form device path. This is currently not supported in the UiApp or Shell built-in commands
It would be nice to configure UEFI network booting in a MAC address independent way.
That would allow us to have a golden image and use it in any other pi. Currently this cannot be done because the boot option seems to be associated with the MAC address, so it cannot be used in a different pi.
The text was updated successfully, but these errors were encountered: