Date: Sat, 23 Feb 2013 17:57:44 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Ian Lepore <ian@FreeBSD.org> Cc: freebsd-hackers@FreeBSD.org Subject: Re: TFTP single file kernel load Message-ID: <alpine.BSF.2.00.1302231755260.4333@wojtek.tensor.gdynia.pl> In-Reply-To: <1361637752.1185.99.camel@revolution.hippie.lan> References: <alpine.BSF.2.00.1302231625440.42204@wojtek.tensor.gdynia.pl> <1361637752.1185.99.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Basically what needs doing is to link the kernel with a modified > ldscript that doesn't add space for the program headers, and then run > the output of that link through "objcopy -S -O binary" to create a > kernel.bin file. That file can be directly loaded to the address it was > linked for, and a jump to the load address launches the kernel. is btxld(8) a tool i have to use after making kernel.bin file? what should i use for -b and -l > Whether the kernel runs properly when launched that way is a different > question. An arm kernel will run that way because we haven't had the > luxury of loader(8) in the arm world until recently. The x86 kernel may > expect values in the environment that the loader obtained from the bios. it can be loaded without loader for now - if you press a key before loader(8) is loaded and enter kernel image. at least it was like that.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1302231755260.4333>