search for: phnum

...\n"; return; } if ($magic !~ /^\x7fELF(.)/) { print "$path: bad magic\n"; return; } my $class = ord($1); my ($ehdrPat, $ehdrSize, $phdrPat, $phdrSize, $phdrFields); my $ehdrFields = [qw{ ident type machine version entry phoff shoff flags ehsize phentsize phnum shentsize shnum shstrndx }]; if ($class == ELFCLASS32) { $ehdrSize = SZ_ELF32HDR; $ehdrPat = "a[16] SS LL LL L SSSSSS"; $phdrSize = SZ_ELF32PHDR; $phdrPat = "LL LL LL LL"; $phdrFields = [qw{ type offset vaddr paddr filesz memsz flags align }]; } elsif...

...64_t); @@ -161,17 +161,16 @@ static void usage(char *progname) int main(int argc, char **argv) { - struct stat st; Elf32_Ehdr e32_hdr; Elf64_Ehdr e64_hdr; __uint32_t entry; __uint8_t class; - __uint64_t shoff; - __uint16_t shnum, shentsize, shstrndx; + __uint64_t phoff = 0; + __uint16_t phnum = 0, phentsize = 0; unsigned char *id; FILE *f_in, *f_out; void *buf; - size_t datasz, rv; + size_t datasz, memsz, rv; if (argc < 3) { usage(argv[0]); @@ -184,11 +183,6 @@ int main(int argc, char **argv) exit(EXIT_FAILURE); } - if (stat(argv[1], &st) != 0) { - perror(&qu...

...64_t); @@ -157,17 +157,16 @@ static void usage(char *progname) int main(int argc, char **argv) { - struct stat st; Elf32_Ehdr e32_hdr; Elf64_Ehdr e64_hdr; __uint32_t entry; __uint8_t class; - __uint64_t shoff; - __uint16_t shnum, shentsize, shstrndx; + __uint64_t phoff = 0; + __uint16_t phnum = 0, phentsize = 0; unsigned char *id; FILE *f_in, *f_out; void *buf; - size_t datasz, rv; + size_t datasz, memsz, rv; if (argc < 3) { usage(argv[0]); @@ -180,11 +179,6 @@ int main(int argc, char **argv) exit(EXIT_FAILURE); } - if (stat(argv[1], &st) != 0) { - perror(&qu...

The PE headers of the generated efi file were quite buggy. And since OVMF perform a few consistency checks, syslinux was unable to run on it. I don't pretend to have a thorough understanding of the PE+ headers, some bugs may remain. :) Celelibi (4): efi: Fix PE header field rva_and_sizes_nr efi: Location, size and alignment of .text section efi: Useless relocations in PE file efi: PE

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series: 1. Updates the boot protocol to version 2.07 2. Clean up the existing build process, to get rid of tools/build and make the linker do more heavy lifting 3. Make the bzImage payload an ELF file. The bootloader can extract this as a naked ELF file by skipping over boot_params.setup_sects worth of 16-bit setup code. 4. Update the boot_params to 2.07, and update the

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some