From 34fc4ab80b507739e2580d490dff67fcfdde11ea Mon Sep 17 00:00:00 2001 From: "Ronald G. Minnich" Date: Mon, 6 Oct 2014 15:30:37 +0000 Subject: mkelfimage: remove It's not been needed for years, is definitely not needed now that cbfstool parses bzImages, and its presence keeps confusing people. Also, rewrite history. We never mentioned mkelfimage in the documentation. Never, ever, ever. Change-Id: Id96a57906ba6a423b06a8f4140d2efde6f280d55 Signed-off-by: Ronald G. Minnich Reviewed-on: http://review.coreboot.org/7021 Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel Reviewed-by: Martin Roth Reviewed-by: Patrick Georgi --- documentation/CorebootBuildingGuide.tex | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-) (limited to 'documentation') diff --git a/documentation/CorebootBuildingGuide.tex b/documentation/CorebootBuildingGuide.tex index 5847daba78..5b3eacf778 100644 --- a/documentation/CorebootBuildingGuide.tex +++ b/documentation/CorebootBuildingGuide.tex @@ -1353,21 +1353,8 @@ utilities suite. Get it at \subsection {Booting Payloads} coreboot can load a payload binary from a Flash device or IDE. This payload can be a boot loader, like FILO or Etherboot, a kernel image, or -any other static ELF binary. - -To create a Linux kernel image, that is bootable in coreboot, you have -to use mkelfImage. The command line I used, looks like follows: - -\begin{verbatim} - objdir/sbin/mkelfImage t bzImagei386 kernel /boot/vmlinuz \ - commandline="console=ttyS0,115200 root=/dev/hda3" \ - initrd=/boot/initrd output vmlinuz.elf -\end{verbatim} - - -This will create the file \texttt{vmlinuz.elf} from a distribution -kernel, console redirected to the serial port and using an initial -ramdisk. +any other static ELF binary. If you specify a bzImage as the payload, +the cbfs utility will figure out how to create a coreboot payload from it. \subsection{Kernel on dhcp/tftp} -- cgit v1.2.3