From: Dave Martin <Dave.Martin@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Makefile: Ensure initrd parameters in /chosen are up-to-date
Date: Tue, 13 May 2025 14:45:07 +0100 [thread overview]
Message-ID: <aCNM42HhLVQIePIS@e133380.arm.com> (raw)
In-Reply-To: <aCIY_bKyj6Pl7ZZm@J2N7QTR9R3>
Hi,
On Mon, May 12, 2025 at 04:51:25PM +0100, Mark Rutland wrote:
> On Mon, May 12, 2025 at 04:09:44PM +0100, Dave Martin wrote:
> > The initrd parameters in the FDT /chosen node are fixed when the device
> > tree blob is generated, so it is important to regenerate the device
> > tree if the initrd image has been updated.
> >
> > Currently this does not happen, so the parameters can be stale.
> > In particular, if the initrd image is bigger than it was when the
> > device tree was first generated then the value of the linux,initrd-end
> > parameter is too small, leading to truncation of the initrd image on
> > boot even though the whole image is present in linux-system.axf.
> >
> > Make $(FILESYSTEM) a dependency of fdt.dtb so that the parameters are
> > refreshed properly based on the current initrd image (if any).
> >
> > Without --with-initrd, FILESYSTEM is the empty string and the
> > dependency evaporates, which is just fine.
> >
> > Signed-off-by: Dave Martin <Dave.Martin@arm.com>
>
> Applied.
>
> Mark.
Thanks!
---Dave
prev parent reply other threads:[~2025-05-13 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 15:09 [PATCH] Makefile: Ensure initrd parameters in /chosen are up-to-date Dave Martin
2025-05-12 15:51 ` Mark Rutland
2025-05-13 13:45 ` Dave Martin [this message]
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=aCNM42HhLVQIePIS@e133380.arm.com \
--to=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
/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