linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org, jcm@printk.net
Subject: Re: Stripped binary insertion with the GNU Linker suggestions (fwd)
Date: Fri, 11 Jul 2003 11:37:16 -0500	[thread overview]
Message-ID: <EE71A277-B3BD-11D7-B05B-000A95A0560C@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10307111655430.25244-100000@router>

On Friday, Jul 11, 2003, at 11:00 US/Central, Jon Masters wrote:
>
> The reason I want it is that I am creating a single elf output file 
> which
> is loaded in to SDRAM by a SystemACE chip and in order for that to work
> correctly I need to give the appropriate tools a single elf input
> containing everything where I want it to be loaded in memory.

Not sure I understand the problem exactly, but I believe ppc32 kernels 
do exactly what you want. Have a look at arch/ppc/boot/ld.script and 
see __{image,ramdisk,sysmap}_begin . Also see how e.g. 
arch/ppc/boot/prep/Makefile uses objcopy 
--add-section=.image=vmlinux.gz .

The end result is taking an arbitrary file and stuffing it into an ELF 
section, then using a linker script to provide the start and end 
addresses of the file data.

-- 
Hollis Blanchard
IBM Linux Technology Center


  reply	other threads:[~2003-07-11 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-11 15:19 Stripped binary insertion with the GNU Linker suggestions (fwd) Jon Masters
2003-07-11 15:35 ` Larry McVoy
2003-07-11 16:00   ` Jon Masters
2003-07-11 16:37     ` Hollis Blanchard [this message]
2003-07-12  1:14       ` Jon Masters

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=EE71A277-B3BD-11D7-B05B-000A95A0560C@us.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=jcm@printk.net \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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;
as well as URLs for NNTP newsgroup(s).