Lines Matching +full:start +full:- +full:from +full:- +full:bottom

5 (NOT a "zephyr.strip" intended for grub/multiboot loading -- we need
9 from the EFI shell.
15 image extracted from a built zephyr.elf file.  EFI applications are
18 appropriate locations at startup, clear any zero-filled (BSS, etc...)
23 load it from the EFI boot filesystem into its correct location with no
26 that size, and potentially MUCH more if you start enabling the default
32 The code and link environment here is non-obvious.  The simple rules
45 Linux toolchain.  EFI binaries are relocatable PE-COFF files --
50 independent code.  Non-static global variables and function addresses
52 time by a system binary (ld-linux.so).  But there is no ld-linux.so in
57 via the x86_64 RIP-relative addressing mode and doesn't rely on any
58 support from the environment.  But that only works for symbols that
59 the compiler (not the linker) knows a-priori will never be in
63 You might ask: why build a position-independent executable in the
64 first place?  Why not just link to a specific address?  The PE-COFF
75 a IP-relative addressing mode, so we'd have to do some kind of
77 a proper PE-COFF toolchain.
82 systems I've tried, EFI uses memory near the top of 32-bit-accessible
83 physical memory, while Zephyr prefers to load into the bottom of RAM
85 could control the Zephyr mapping addresses per-platform if needed to