From: Ralf Baechle <ralf@linux-mips.org>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Can you add a signature to the kernel ELF image?
Date: Tue, 24 Nov 2009 23:44:06 +0000 [thread overview]
Message-ID: <20091124234406.GB20316@linux-mips.org> (raw)
In-Reply-To: <4B0C625B.5070408@shikadi.net>
On Wed, Nov 25, 2009 at 08:46:51AM +1000, Adam Nielsen wrote:
> I'm trying to port the kernel to an NCD HMX X-Terminal (MIPS R4600), but
> the one thing I have to do before I can actually boot the image is attach
> a signature to it. I have the signature 'code' in assembly[1], but I'm
> not sure how to link it so that it ends up as the first bit of code in
> the ELF image (the very first instruction is a 'b' to jump over the
> actual signature text.)
>
> Without this the boot monitor will refuse to boot the kernel. Any
> suggestions as to how I might accomplish this?
Take a look at arch/mips/kernel/head.S. This file will be the first on
the final linker call's command line, that is head.S's .text section will
end at the lowest address.
In head.S there is this
#ifdef CONFIG_BOOT_RAW
/*
* Give us a fighting chance of running if execution beings at the
* kernel load address. This is needed because this platform does
* not have a ELF loader yet.
*/
FEXPORT(__kernel_entry)
j kernel_entry
#endif
ifdef. Add your own magic stuff there, something like
#ifdef CONFIG_NCD_HMX
b 1f
nop
nop
.word 0x20
.asciz "XncdHMX"
.word 0, 0, 0
#endif
> [1] http://www.linux-mips.org/wiki/HMX
The wiki page says something about a CRC but just poking a 0x20 into a
constant address is not exactly a CRC calculation. Not sure how this
really is meant.
Ralf
next prev parent reply other threads:[~2009-11-24 23:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 22:46 Can you add a signature to the kernel ELF image? Adam Nielsen
2009-11-24 23:39 ` David Daney
2009-11-24 23:44 ` Ralf Baechle [this message]
2009-11-25 11:34 ` Adam Nielsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091124234406.GB20316@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=a.nielsen@shikadi.net \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox