linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: remove the 4x expansion presumption while decompressing the kernel
Date: Thu, 17 Feb 2011 13:56:52 -0600	[thread overview]
Message-ID: <4D5D7D84.1040209@gmail.com> (raw)
In-Reply-To: <20110217185223.GA30606@n2100.arm.linux.org.uk>

On 02/17/2011 12:52 PM, Russell King - ARM Linux wrote:
> On Thu, Feb 17, 2011 at 10:51:56AM -0700, Grant Likely wrote:
>> As for knowing where it can relocate to, we already know (actually
>> current code just makes an assumption) about how long the kernel
>> proper image is and where it wants to live in the zImage's head.S.
>> Assuming enough ram, if r6 reflects the size of the zImage + the size
>> of the appended data then it should be good.
>
> That isn't a valid argument.  Just because "the decompressor already
> does it" does not mean that it'll work with ramdisks.  We've been
> lucky so far that it has worked with the kernel - and that's exactly
> what it is - luck.
>
> It works for a 1-2MB kernel.  A 16MB ramdisk is a completely different
> kettle of bytes.

The capability to add an initramfs into the kernel binary already exists 
within the kernel build system. The primary difference here is when the 
initramfs is added. Doing that after the kernel build is the more sane 
approach. For example, if you want to include kernel modules in your 
initramfs and a single image, the current method is kind of broken. You 
have to build the kernel once to build the modules, then build it again 
to update the initramfs.

If the ramdisk size is the only issue, then you would be okay with 
adding couple of KB of dtb image?

Rob

>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2011-02-17 19:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 21:39 [PATCH 1/2] ARM: improvements to compressed/head.S Nicolas Pitre
2011-02-16 21:39 ` [PATCH 2/2] ARM: remove the 4x expansion presumption while decompressing the kernel Nicolas Pitre
2011-02-16 21:55   ` Stephen Boyd
2011-02-16 22:11     ` Nicolas Pitre
2011-02-16 22:14       ` Stephen Boyd
2011-02-17  0:09   ` Grant Likely
2011-02-17  1:48     ` Nicolas Pitre
2011-02-17  4:33       ` Grant Likely
2011-02-17  9:26     ` Russell King - ARM Linux
2011-02-17 17:51       ` Grant Likely
2011-02-17 18:52         ` Russell King - ARM Linux
2011-02-17 19:56           ` Rob Herring [this message]
2011-02-17 20:40           ` Nicolas Pitre
2011-03-08  6:37   ` Jean-Christophe PLAGNIOL-VILLARD

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=4D5D7D84.1040209@gmail.com \
    --to=robherring2@gmail.com \
    --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).