| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <87a5b0800807110332y65ea8c15g2feaa8806b1f1d85@mail.gmail.com> Date: Fri, 11 Jul 2008 11:32:01 +0100 From: "Will Newton" <will.newton@...il.com> To: "Luke -Jr" <luke@...hjr.org> Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: Re: kernel_entry up front On Fri, Jul 11, 2008 at 5:08 AM, Luke -Jr <luke@...hjr.org> wrote: > I need to get kernel_entry to the lowest memory region in the binary. This is > because a platform I am porting to does not support ELF, and always begins > execution at the first word of the firmware image. Alternatively, if there is > a simpler way to prepend the image with a jump to the kernel_entry symbol, > that could work as well. The easiest way to do this is to put your entry point in a named section (for example .text.head) then edit vmlinux.lds.S to put that section at the correct place in your kernel image. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists