From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: saeed bishara <saeed.bishara@gmail.com>,
Paolo Ornati <ornati@fastwebnet.it>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
Linux-arm-toolchain@lists.arm.linux.org.uk
Subject: Re: add new code section for kernel code
Date: Fri, 7 Apr 2006 16:43:50 +0100 [thread overview]
Message-ID: <20060407154349.GB31458@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1144422864.3117.0.camel@laptopd505.fenrus.org>
On Fri, Apr 07, 2006 at 05:14:24PM +0200, Arjan van de Ven wrote:
> On Fri, 2006-04-07 at 14:02 +0300, saeed bishara wrote:
> > I noticed the arch/arm/boot/compressed/ files compiled with
> > ffunction-sections switch, so I added the -fno-function-sections to
> > the EXTRA_CFLAGS of the compressed/Makefile. And this solved the
> > problem.
>
> can you send a patch for this to Russell ?
I'd prefer not to paper over such bugs. Maybe the following patch will
fix the decompressor for saeed?
diff --git a/arch/arm/boot/compressed/vmlinux.lds.in b/arch/arm/boot/compressed/vmlinux.lds.in
--- a/arch/arm/boot/compressed/vmlinux.lds.in
+++ b/arch/arm/boot/compressed/vmlinux.lds.in
@@ -18,6 +18,7 @@ SECTIONS
_start = .;
*(.start)
*(.text)
+ *(.text.*)
*(.fixup)
*(.gnu.warning)
*(.rodata)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-04-07 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 12:45 add new code section for kernel code saeed bishara
2006-04-06 13:10 ` Paolo Ornati
2006-04-06 15:27 ` saeed bishara
2006-04-06 16:47 ` saeed bishara
2006-04-07 11:02 ` saeed bishara
2006-04-07 15:14 ` Arjan van de Ven
2006-04-07 15:43 ` Russell King [this message]
2006-04-09 9:53 ` saeed bishara
2006-04-09 20:30 ` Russell King
2006-04-10 7:11 ` saeed bishara
2006-04-10 9:12 ` Dimitry Andric
2006-04-11 14:49 ` saeed bishara
2006-04-12 5:34 ` Arjan van de Ven
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=20060407154349.GB31458@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Linux-arm-toolchain@lists.arm.linux.org.uk \
--cc=arjan@infradead.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
--cc=saeed.bishara@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.