From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: rpi: set initrd_high
Date: Sun, 14 Feb 2016 12:30:00 -0700 [thread overview]
Message-ID: <56C0D5B8.5060305@wwwdotorg.org> (raw)
In-Reply-To: <1455474204-827-1-git-send-email-lkundrak@v3.sk>
On 02/14/2016 11:23 AM, Lubomir Rintel wrote:
> The kernel gets much too sad when the ramdisk is loaded too high into the 1GiB
> of memory on Raspberry Pi 2:
>
> ## Flattened Device Tree blob at 00000100
> Booting using the fdt blob at 0x000100
> Loading Ramdisk to 39c14000, end 3ab45067 ... OK
> Using Device Tree in place at 00000100, end 000045ea
> ...
> [ 0.599346] Unpacking initramfs...
> [ 0.602924] Unable to handle kernel paging request at virtual address f9c14000
>
> Placement of the device tree was fixed in 89ca1000 (ARM: rpi: set fdt_high
> in the default environment).
Acked-by: Stephen Warren <swarren@wwwdotorg.org>
next prev parent reply other threads:[~2016-02-14 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 18:23 [U-Boot] [PATCH] ARM: rpi: set initrd_high Lubomir Rintel
2016-02-14 19:30 ` Stephen Warren [this message]
2016-02-15 22:35 ` [U-Boot] " Tom Rini
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=56C0D5B8.5060305@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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