All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Tom Rini <trini@konsulko.com>
Cc: Sam Protsenko <semen.protsenko@linaro.org>,
	Richard Weinberger <richard@nod.at>,
	upstream@sigma-star.at, u-boot@lists.denx.de,
	ddrokosov@salutedevices.com, sjg@chromium.org,
	tharvey@gateworks.com, ilias.apalodimas@linaro.org,
	kojima.masahisa@socionext.com, upstream+uboot@sigma-star.at
Subject: Re: [RFC, PATCH] fdt: Make sure there is no stale initrd left
Date: Sat, 04 Oct 2025 10:05:43 +0200	[thread overview]
Message-ID: <5561663.0HT0TaD9VG@nailgun> (raw)
In-Reply-To: <20251003210149.GA6093@bill-the-cat>

On Freitag, 3. Oktober 2025 23:01 Tom Rini wrote:
> > My current way to work around the problem is having these commands in
> > my U-Boot scripts:
> > 
> > fdt addr $fdt_addr
> > fdt rm /chosen linux,initrd-start
> > fdt rm /chosen linux,initrd-end
> 
> I do wonder if the best path forward is adding some opt-in CONFIG option
> here?

Hm, yes. Maybe something like CONFIG_FDT_INITRD_EXPLIZIT which is enabled
by default for the RPi target?

Thanks,
//richard

-- 
​​​​​sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT UID/VAT Nr:
ATU 66964118 | FN: 374287y



  reply	other threads:[~2025-10-04  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 15:02 [RFC, PATCH] fdt: Make sure there is no stale initrd left Richard Weinberger
2025-06-12 22:15 ` Tom Rini
2025-07-08 22:58   ` Sam Protsenko
2025-07-09  6:24     ` Richard Weinberger
2025-07-09 17:05       ` Sam Protsenko
2025-07-10 14:40         ` Richard Weinberger
2025-07-10 17:20           ` Sam Protsenko
2025-09-20 23:01             ` Sam Protsenko
2025-10-03 19:09               ` Richard Weinberger
2025-10-03 21:01                 ` Tom Rini
2025-10-04  8:05                   ` Richard Weinberger [this message]
2025-10-17 22:08                     ` 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=5561663.0HT0TaD9VG@nailgun \
    --to=richard@sigma-star.at \
    --cc=ddrokosov@salutedevices.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kojima.masahisa@socionext.com \
    --cc=richard@nod.at \
    --cc=semen.protsenko@linaro.org \
    --cc=sjg@chromium.org \
    --cc=tharvey@gateworks.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=upstream+uboot@sigma-star.at \
    --cc=upstream@sigma-star.at \
    /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.