linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] Re-organize linker layouts
Date: Thu, 7 Jul 2011 23:36:20 +0100	[thread overview]
Message-ID: <20110707223620.GG20403@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4E15ECB6.40100@codeaurora.org>

On Thu, Jul 07, 2011 at 10:28:22AM -0700, Stephen Boyd wrote:
> On 07/06/2011 03:22 AM, Russell King - ARM Linux wrote:
> > The following series of patches are targetted at two issues:
> >
> > 1. Fixing large initramfs causing PC24 relocations to become out of
> >    range.  This fixes both modules and link-time errors.
> >
> > 2. Making the vmlinux easier to pinpoint the various section-built
> >    data structures and inspect them later.
> >
> > For the main kernel, this allows the size of various sections to be
> > determined via objdump -h.  This also aids objdump -d and -s usage
> > when asking it to target a particular section.
> >
> > For the decompressor, it means that it is now trivially possible to copy
> > out the compressed kernel vmlinux image by:
> >
> >   arm-linux-objcopy -O binary -j .piggydata arch/arm/boot/compressed/vmlinux \
> > 	piggy.gz
> >
> > and thereby obtain the binary kernel image (the Image file) which was
> > originally used.
> 
> I gave this series a test with my poison initmem patch and all looks well
> 
> Tested-by: Stephen Boyd <sboyd@codeaurora.org>
> 
> except for patch 2 as I didn't use a zImage.

Oh, what did you use instead?  I thought no one used the Image files
anymore...

  reply	other threads:[~2011-07-07 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 10:22 [PATCH 0/7] Re-organize linker layouts Russell King - ARM Linux
2011-07-06 10:23 ` [PATCH 1/7] ARM: ensure tag tables are const Russell King - ARM Linux
2011-07-06 10:23 ` [PATCH 2/7] ARM: decompressor: use better output sections Russell King - ARM Linux
2011-07-06 10:23 ` [PATCH 3/7] ARM: vmlinux.lds: move discarded sections to beginning Russell King - ARM Linux
2011-07-06 10:24 ` [PATCH 4/7] ARM: vmlinux.lds: rearrange .init output section Russell King - ARM Linux
2011-07-06 10:24 ` [PATCH 5/7] ARM: vmlinux.lds: remove .rodata/.rodata1 from main .text segment Russell King - ARM Linux
2011-07-06 10:24 ` [PATCH 6/7] ARM: vmlinux.lds: move init sections between text and data sections Russell King - ARM Linux
2011-07-06 10:25 ` [PATCH 7/7] ARM: vmlinux.lds: use _text and _stext the same way as x86 Russell King - ARM Linux
2011-07-06 15:09 ` [PATCH 0/7] Re-organize linker layouts Nicolas Pitre
2011-07-07 17:28 ` Stephen Boyd
2011-07-07 22:36   ` Russell King - ARM Linux [this message]
2011-07-08  0:55     ` Stephen Boyd
2011-07-08  9:07       ` Russell King - ARM Linux
2011-07-08 13:46         ` Nicolas Pitre
2011-07-08 16:03           ` Russell King - ARM Linux
2011-07-08 16:56             ` Stephen Boyd
2011-07-08 18:24               ` Nicolas Pitre
2011-07-11 20:17                 ` Stephen Boyd
2011-07-11 22:14                   ` Nicolas Pitre
2011-07-19 17:22                     ` David Brown
2011-07-19 18:02                       ` Nicolas Pitre
2011-07-19 20:42                         ` David Brown

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=20110707223620.GG20403@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).