From: Tuomas Tynkkynen <tuomas.tynkkynen@iki.fi>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] ARM: qemu-arm: define fdt_addr_r
Date: Mon, 15 Oct 2018 04:01:06 +0300 [thread overview]
Message-ID: <20181015040106.78c6f7a2@thinkpad> (raw)
In-Reply-To: <20181012050757.6925-2-takahiro.akashi@linaro.org>
Hi Takahiro,
On Fri, 12 Oct 2018 14:07:57 +0900
AKASHI Takahiro <takahiro.akashi@linaro.org> wrote:
> This variable, fdt_addr_t, is missing in the current qemu-arm.h while
> it seems to be mandatory, at least, to run distro_bootcmd as expected.
> So just add its definition. A size of 1MB would be enough.
>
In what way is this required for distro_bootcmd to work? At least in the
past I've tested qemu_arm64_defconfig and EFI boot with the Fedora
netinst image and it has worked fine in stock U-Boot.
Note that these '-machine virt' based targets are slightly different
from real hardware in the sense that instead of loading a .dtb file
provided by the OS, the device tree is provided by QEMU. In the hunk
below you can see "fdt_addr=0x40000000\0" providing the address of
the QEMU-provided device tree which the distro scripts should be
using.
I guess in principle having ${fdt_addr_r} set as well shouldn't hurt and
might be used for testing/unusual purposes. Glancing at cmd/pxe.c,
there is a problem though, in that if ${fdt_addr_r} were defined, a PXE
file using the FDTDIR directive would attempt loading a dtb file named
"<NULL>-qemu-arm.dtb" instead of falling back to using ${fdt_addr}.
That bug would need to be fixed first before applying this patch.
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> ---
> include/configs/qemu-arm.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/configs/qemu-arm.h b/include/configs/qemu-arm.h
> index 91fb8d47edf8..0e66f946dde5 100644
> --- a/include/configs/qemu-arm.h
> +++ b/include/configs/qemu-arm.h
> @@ -55,6 +55,7 @@
> "fdt_high=0xffffffff\0" \
> "initrd_high=0xffffffff\0" \
> "fdt_addr=0x40000000\0" \
> + "fdt_addr_r=0x40100000\0" \
> "scriptaddr=0x40200000\0" \
> "pxefile_addr_r=0x40300000\0" \
> "kernel_addr_r=0x40400000\0" \
next prev parent reply other threads:[~2018-10-15 1:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 5:07 [U-Boot] [PATCH 1/2] efi_loader: rework fdt handling in distro boot script AKASHI Takahiro
2018-10-12 5:07 ` [U-Boot] [PATCH 2/2] ARM: qemu-arm: define fdt_addr_r AKASHI Takahiro
2018-10-15 1:01 ` Tuomas Tynkkynen [this message]
2018-10-15 5:14 ` AKASHI Takahiro
2018-10-16 13:04 ` Alexander Graf
2018-10-17 22:25 ` Tuomas Tynkkynen
2018-10-18 7:25 ` Alexander Graf
2018-10-19 6:33 ` AKASHI Takahiro
2018-10-19 7:46 ` Alexander Graf
2018-10-19 8:17 ` AKASHI Takahiro
2018-10-24 10:36 ` Tuomas Tynkkynen
2018-10-16 13:15 ` [U-Boot] [PATCH 1/2] efi_loader: rework fdt handling in distro boot script Alexander Graf
2018-10-18 2:07 ` AKASHI Takahiro
2018-10-18 7:31 ` Alexander Graf
2018-10-19 7:20 ` AKASHI Takahiro
2018-10-19 7:31 ` Alexander Graf
2018-10-19 8:32 ` AKASHI Takahiro
2018-10-19 8:50 ` Alexander Graf
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=20181015040106.78c6f7a2@thinkpad \
--to=tuomas.tynkkynen@iki.fi \
--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