From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Can physical flash initramfs cpio address be given to bootm?
Date: Mon, 22 Mar 2010 10:08:54 +0100 [thread overview]
Message-ID: <20100322090854.GB10684@pengutronix.de> (raw)
In-Reply-To: <20100319123616.GC21280@n2100.arm.linux.org.uk>
Hello,
On Fri, Mar 19, 2010 at 12:36:16PM +0000, Russell King - ARM Linux wrote:
> On Wed, Mar 17, 2010 at 03:09:14PM -0400, Brian Hutchinson wrote:
> > 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.
>
> bootm has nothing to do with the kernel, so I think you want to ask
> this question on a different (uboot?) mailing list.
>
> > 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
>
> The initrd image must be in RAM; there's no getting around this because
> the kernel wants to convert addresses to struct page pointers and other
> magical stuff like that which can only be done with RAM.
Is this a problem of the implementation or a techical one? Some time
ago we hit the same problem and IIRC it was only that the memory was
allocated before unpacking and freed at the end. If that's the only
issue than we can skip it if the initrd lives outside RAM!?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-03-22 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 19:09 Can physical flash initramfs cpio address be given to bootm? Brian Hutchinson
2010-03-19 12:36 ` Russell King - ARM Linux
2010-03-22 9:08 ` Uwe Kleine-König [this message]
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=20100322090854.GB10684@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).