diff options
| author | Michael Brown | 2024-03-05 21:20:10 +0100 |
|---|---|---|
| committer | Michael Brown | 2024-03-06 13:19:22 +0100 |
| commit | 636ccb4ca55c73841e634f9d5986087fb3565da4 (patch) | |
| tree | 31a788498a6a03bfead3a7df5c8da9ef13eab8b9 /src/core/null_sanboot.c | |
| parent | [efi] Allow booting from local disks via the "sanboot" command (diff) | |
| download | ipxe-636ccb4ca55c73841e634f9d5986087fb3565da4.tar.gz ipxe-636ccb4ca55c73841e634f9d5986087fb3565da4.tar.xz ipxe-636ccb4ca55c73841e634f9d5986087fb3565da4.zip | |
[block] Allow for additional SAN boot parameters alongside filename
The drive specification alone does not necessarily contain enough
information to perform a SAN boot (or local disk boot) under UEFI. If
the next-stage bootloader is installed in the EFI system partition
under a non-standard name (e.g. "\EFI\debian\grubx64.efi") then this
explicit boot filename must also be specified.
Generalise this concept to use a "SAN boot configuration parameters"
structure (currently containing only the optional explicit boot
filename), to allow for easy expansion to provide other parameters
such as the partition UUID or volume label.
Signed-off-by: Michael Brown <mcb30@ipxe.org>
Diffstat (limited to 'src/core/null_sanboot.c')
| -rw-r--r-- | src/core/null_sanboot.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/null_sanboot.c b/src/core/null_sanboot.c index 7c0680f5..2340cd2a 100644 --- a/src/core/null_sanboot.c +++ b/src/core/null_sanboot.c @@ -38,7 +38,7 @@ static void null_san_unhook ( unsigned int drive __unused ) { } static int null_san_boot ( unsigned int drive __unused, - const char *filename __unused ) { + struct san_boot_config *config __unused ) { return -EOPNOTSUPP; } |