From: Peter Maydell <peter.maydell@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH qemu v3] device_tree: Increase FDT_MAX_SIZE to 1 MiB
Date: Mon, 16 Apr 2018 13:20:29 +0100 [thread overview]
Message-ID: <CAFEAcA-8yd9oKu1_FTxRHs1w_q7O5c1K7+n9s-BO3_WW8+Piog@mail.gmail.com> (raw)
In-Reply-To: <1523541337-23919-1-git-send-email-geert+renesas@glider.be>
On 12 April 2018 at 14:55, Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> It is not uncommon for a contemporary FDT to be larger than 64 KiB,
> leading to failures loading the device tree from sysfs:
>
> qemu-system-aarch64: qemu_fdt_setprop: Couldn't set ...: FDT_ERR_NOSPACE
>
> Hence increase the limit to 1 MiB, like on PPC.
>
> For reference, the largest arm64 DTB created from the Linux sources is
> ca. 75 KiB large (100 KiB when built with symbols/fixup support).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v3:
> - Update example size figures,
>
> v2:
> - Enlarge from 128 KiB to 1 MiB, as suggested by Peter Maydell.
> ---
> device_tree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks; applied to target-arm.next for 2.13. I'll add cc:qemu-stable too.
-- PMM
WARNING: multiple messages have this Message-ID (diff)
From: Peter Maydell <peter.maydell@linaro.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH qemu v3] device_tree: Increase FDT_MAX_SIZE to 1 MiB
Date: Mon, 16 Apr 2018 13:20:29 +0100 [thread overview]
Message-ID: <CAFEAcA-8yd9oKu1_FTxRHs1w_q7O5c1K7+n9s-BO3_WW8+Piog@mail.gmail.com> (raw)
In-Reply-To: <1523541337-23919-1-git-send-email-geert+renesas@glider.be>
On 12 April 2018 at 14:55, Geert Uytterhoeven <geert+renesas@glider.be> wrote:
> It is not uncommon for a contemporary FDT to be larger than 64 KiB,
> leading to failures loading the device tree from sysfs:
>
> qemu-system-aarch64: qemu_fdt_setprop: Couldn't set ...: FDT_ERR_NOSPACE
>
> Hence increase the limit to 1 MiB, like on PPC.
>
> For reference, the largest arm64 DTB created from the Linux sources is
> ca. 75 KiB large (100 KiB when built with symbols/fixup support).
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v3:
> - Update example size figures,
>
> v2:
> - Enlarge from 128 KiB to 1 MiB, as suggested by Peter Maydell.
> ---
> device_tree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks; applied to target-arm.next for 2.13. I'll add cc:qemu-stable too.
-- PMM
next prev parent reply other threads:[~2018-04-16 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 13:55 [PATCH qemu v3] device_tree: Increase FDT_MAX_SIZE to 1 MiB Geert Uytterhoeven
2018-04-12 13:55 ` [Qemu-devel] " Geert Uytterhoeven
2018-04-16 12:20 ` Peter Maydell [this message]
2018-04-16 12:20 ` Peter Maydell
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=CAFEAcA-8yd9oKu1_FTxRHs1w_q7O5c1K7+n9s-BO3_WW8+Piog@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.