Daniel Verkamp 3007ff3cf4 x86_64: load initrd at max address ... This matches behavior of other bootloaders (grub2, iPXE), and the kernel seems to be relying on this; decompression of the initrd fails if the initrd is loaded right after the kernel as before, but succeeds if loaded at the maximum address. BUG=None TEST=Boot Debian kernel + initrd on workstation Change-Id: If7712efb05f55ef413a419dfe276ed3f68c335b7 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1616989 Tested-by: kokoro <noreply+kokoro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>		2019-05-20 15:47:23 -07:00
..
src	x86_64: load initrd at max address	2019-05-20 15:47:23 -07:00
Cargo.toml	cargo: Sort all dependency lists in Cargo.toml	2019-04-09 01:55:14 -07:00