libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Clarified that El Torito images for EFI always get their own size as load size

Browse Source
This commit is contained in:
Thomas Schmitt
2024-12-20 17:37:29 +01:00
parent 362a17c571
commit 23f28b97e5
6 changed files with 96 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
xorriso/xorriso.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISO 1 "Version 1.5.7, Dec 08, 2024"
.TH XORRISO 1 "Version 1.5.7, Dec 19, 2024"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -4035,9 +4035,9 @@ The default "no_emulation" is suitable for ISOLINUX, GRUB, FreeBSD cdboot.
Default for legacy BIOS is 2048 which matches the expectations of most BIOS
boot images. The special value "full" means the full size of the boot image
file rounded up to a multiple of 2048 bytes. Maximum is 33,552,384 bytes.
With EFI boot images the default is the full image size. Images which exceed
the maximum size get size 0 or 1, which means "up to the end of the device"
according to the UEFI specification.
With EFI boot images the load size is always the full image size.
Images which exceed the maximum size get size 0 or 1, which means
"up to the end of the device" according to the UEFI specification.
.br
\fBboot_info_table=on\fR causes address patching to bytes 8 to 63
of the boot image which is given by "any" "bin_path=".