From: Tuomas Tynkkynen <tuomas@tuxera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] rpi: Adjust fdt_addr_r to a sane address
Date: Sun, 22 Apr 2018 22:41:55 +0300 [thread overview]
Message-ID: <20180422224155.342886b7@duuni> (raw)
In-Reply-To: <20180420100349.27194-1-tuomas@tuxera.com>
On Fri, 20 Apr 2018 13:03:47 +0300
Tuomas Tynkkynen <tuomas@tuxera.com> wrote:
> Hi Alexander,
>
> What do you think of these patches? I haven't done testing with the
> big kernels / DTBs yet, just that my previously-working kernel still
> boots.
>
I've now verified that these two patches work as expected. I tested:
- RPi 1 running mainline kernel
- RPi 1 running downstream kernel
- RPi 3 running mainline kernel in 64-bit mode
- RPi 3 running mainline kernel in 32-bit mode
- RPi 3 running downstream kernel in 32-bit mode
- RPi 3B+ running downstream kernel in 32-bit mode
This was with the extlinux.conf distro boot. I don't know to what
extent these variables affect EFI boot.
> Tuomas Tynkkynen (2):
> rpi: Fix fdt_high & initrd_high for 64-bit builds
> rpi: Change load addresses to make more room for the kernel & DTB
>
next prev parent reply other threads:[~2018-04-22 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 15:49 [U-Boot] [PATCH] rpi: Adjust fdt_addr_r to a sane address Alexander Graf
2018-04-14 18:04 ` Tuomas Tynkkynen
2018-04-20 10:03 ` Tuomas Tynkkynen
2018-04-20 10:03 ` [U-Boot] [PATCH 1/2] rpi: Fix fdt_high & initrd_high for 64-bit builds Tuomas Tynkkynen
2018-05-24 7:51 ` Alexander Graf
2018-05-24 14:57 ` Tuomas Tynkkynen
2018-05-24 15:22 ` Alexander Graf
2018-04-20 10:03 ` [U-Boot] [PATCH 2/2] rpi: Change load addresses to make more room for the kernel & DTB Tuomas Tynkkynen
2018-04-22 19:41 ` Tuomas Tynkkynen [this message]
2018-05-24 8:12 ` [U-Boot] [PATCH] rpi: Adjust fdt_addr_r to a sane address Alexander Graf
2018-05-24 11:07 ` Tuomas Tynkkynen
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=20180422224155.342886b7@duuni \
--to=tuomas@tuxera.com \
--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