linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Przybylski <Frank.Przybylski@vas-gmbh.de>
To: linuxppc-embedded@lists.linuxppc.org
Cc: Kwansuk Kim <kskim@neowave.co.kr>
Subject: Re: omitted kernel sections
Date: Tue, 27 Jun 2000 15:42:22 +0200	[thread overview]
Message-ID: <3958AF3E.32693109@vas-gmbh.de> (raw)
In-Reply-To: 4.3.2.20000626080626.00b482e0@falcon.si.com


Hi,

Jerry Van Baren wrote:
>
> Jon Diekema and I tried Wolfgang's "load" flag hint with the EST JTAG
> debugger and were unsuccessful.  We were unable to use objcopy to make
> the extra sections loadable.  We are guessing that you have to set the
> loadable flag, but you also have to label the section ".text" for the
> tools that are giving problems (EST in our case).  Jon produced a patch
> (based on work by Arto Vuori) which goes into the makefile and makes
> valid loadable sections out of the gzimage (compressed kernel) and the
> rdimage (initial ramdisk) sections.
>

I'd guess it's more important to adjust the VMA than the section's name to tell
the loader where to put the sections content.

If you examine the section's listing you'll notice address zero for .image and
.initrd, so only setting the load flag won't do the job.

I only prepare the kernel image (right now, I don't use .initrd) for loading
with the following objcopy call:

'powerpc-linux-objcopy \
 --set-section-flags=image=contents,alloc,load,readonly,data \
 --adjust-section-vma=image=$(powerpc-linux-objdump -h $kernel/zvmlinux | \
 grep .bss | awk '{print "0x"$4}') \
 $kernel/zvmlinux \
 $kernel/zvmlinux2'

To be on the secure side one should correct the vma's of .image to fit behind
.bss and of .initrd behind .image.

I thought someone patched the makefile to do this? (I guess, I'm not working on
the actual sources, but I don't like the idea behind bitkeeper very much
either...)

hth
	Frank

--
===============================================================================
Frank Przybylski,VAS GmbH,Gotenstr.6,20097 Hamburg,GERMANY,TEL:+49-40-238568-14
   mailto:Frank.Przybylski@vas-gmbh.de , visit us at http://www.vas-gmbh.de
===============================================================================

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-06-27 13:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-26  0:53 I am looking for 8xxrom with ethernet(TFTP) jinoung kim
2000-06-26  6:43 ` omitted kernel sections Kwansuk Kim
2000-06-26  8:08   ` Wolfgang Denk
2000-06-26 12:48     ` Jerry Van Baren
2000-06-26 14:40       ` Murray Jensen
2000-06-26 15:18         ` Steven Tarr
2000-06-26 15:46         ` Jerry Van Baren
2000-06-26 16:04       ` Wolfgang Denk
2000-06-26 16:40         ` Jerry Van Baren
2000-06-26 21:57       ` Dan Malek
2000-06-27 13:42       ` Frank Przybylski [this message]
2000-06-26  8:18   ` Matt Porter

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=3958AF3E.32693109@vas-gmbh.de \
    --to=frank.przybylski@vas-gmbh.de \
    --cc=kskim@neowave.co.kr \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).