|
From: Ken Y. <ke...@nl...> - 2001-01-09 02:41:05
|
|What do you need a section header for? Sections aren't really applicable |to programs, just relocatable content. |You should only need to care about Program Headers. At least one is needed otherwise objdump complains. And reading the spec carefully you will see that the 0th entry is needed, it's a NULL entry. |> + Added code to support non-MULTIBOOT ELF when IMAGE_ELF is selected but |> IMAGE_MULTIBOOT is not. Booting from images created by mkelf-linux |> now works! | |I definentily need to review this and get a little discussion going. |I have patches for linux to add a syscall to boot ELF images, |on both x86 & alpha. | |It would be nice if etherboot had a compatible format. I intend to |start writing just what beyond the elf format will be needed to be |compatible. I'm just using ELF format as a container. You can continue to use IMAGE_MULTIBOOT. My changes affect only what happens when IMAGE_MULTIBOOT is not selected, which was undefined prior to my changes. Seeing as the Linux kernel image file is actually a 3 section image, and the sections are not the traditional code, data, bss at all; the addresses in the image are tied to real physical addresses (no relocation data) and real devices, what can your Linux patch sensibily do when given an Etherboot ELF image? |
