linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: b.hutchman@gmail.com (Brian Hutchinson)
To: linux-arm-kernel@lists.infradead.org
Subject: Can physical flash initramfs cpio address be given to bootm?
Date: Wed, 17 Mar 2010 15:09:14 -0400	[thread overview]
Message-ID: <3d1967ab1003171209j43a9a005l4be5d2faf38fec31@mail.gmail.com> (raw)

Can I use the physical flash address of a initramfs with the u-boot
bootm command?  The kernel doesn't appear to like it .... see below.

I'm currently loading my cpio initramfs into u-boot via tftp and then
providing the initrd= bootarg which works now that I've changed my
memory model to sparsemem (Thanks Russell!).

I've tried to wrap the cpio with mkimage both with -a 0x0 -e 0x0 and a
RAM address such as -a 0x4000000 -e 0x4000000 (the location I tftp the
initramfs to)

When I do a bootm 0x20080000 (physical flash location of kernel)
0x20280000 (mkimage of cpio.gz made with -T ramdisk) the physical
flash address of the initramfs gets passed to kernel via ATAGS and the
kernel doesn't like it:

INITRD: 0x20280040+0x00c8bdb6 extends beyond physical memory - disabling initrd

I thought I saw a patch that allowed initramfs to come from physical
media (flash) but it looks like I currently have to copy the initramfs
to ram right now and provide the initrd= which I would like to get
away from since I don't want to have to touch u-boot env vars every
time the cpio changes.

How do you all load a initramfs from flash???

Regards,

Brian

             reply	other threads:[~2010-03-17 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 19:09 Brian Hutchinson [this message]
2010-03-19 12:36 ` Can physical flash initramfs cpio address be given to bootm? Russell King - ARM Linux
2010-03-22  9:08   ` Uwe Kleine-König
2010-03-22 17:54     ` Brian Hutchinson

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=3d1967ab1003171209j43a9a005l4be5d2faf38fec31@mail.gmail.com \
    --to=b.hutchman@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).