From: Olaf Hering <olh@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] generate COFF zImage in arch/powerpc/boot
Date: Fri, 18 Nov 2005 23:13:09 +0100 [thread overview]
Message-ID: <20051118221309.GA12724@suse.de> (raw)
In-Reply-To: <20051118075158.GB14865@suse.de>
On Fri, Nov 18, Olaf Hering wrote:
> On Fri, Nov 18, Paul Mackeras wrote:
>
>
> > +++ merge-hack/arch/powerpc/boot/zImage.lds 2005-11-16 23:16:48.000000000 +1100
>
> This change makes arch/powerpc/boot/README obsolete.
> Last time I looked, the COFF loader liked only .text, .data and .bss.
> But maybe hack-coff needs some tweaking to modify also other sections.
I tried to keep the kernel in its own section. But the firmware does not
fully setup the memory range for that section. claim and map calls for
that area are not enough.
So we either need a ld script for coff with kernel and initrd in the
.data section. Or we write a tool to extract the vmlinux.gz and initrd
based on nm or readelf -a output.
--
short story of a lazy sysadmin:
alias appserv=wotan
next prev parent reply other threads:[~2005-11-18 22:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 6:06 [PATCH] generate COFF zImage in arch/powerpc/boot Paul Mackerras
2005-11-18 7:51 ` Olaf Hering
2005-11-18 22:13 ` Olaf Hering [this message]
2005-11-18 23:16 ` Olaf Hering
2005-11-19 3:45 ` Paul Mackerras
2005-11-19 8:46 ` Olaf Hering
2005-11-19 9:12 ` Olaf Hering
2005-11-19 10:29 ` Olaf Hering
2005-11-19 17:29 ` Olaf Hering
2005-11-19 20:47 ` Olaf Hering
2005-11-23 20:21 ` Olaf Hering
2005-11-23 22:35 ` Paul Mackerras
2005-11-23 22:38 ` Olaf Hering
2005-11-23 22:58 ` Olaf Hering
2005-11-23 23:06 ` Paul Mackerras
2005-12-10 18:31 ` Olaf Hering
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=20051118221309.GA12724@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).