U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Adriano Cordova <adrianox@gmail.com>,
	Andrew Goodbody <andrew.goodbody@linaro.org>,
	Christian Marangi <ansuelsmth@gmail.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Patrice Chotard <patrice.chotard@foss.st.com>,
	Sam Edwards <cfsworks@gmail.com>, Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH 0/3] Synchronize DTC to 1.7.2
Date: Thu, 20 Nov 2025 21:14:09 +0100	[thread overview]
Message-ID: <49969be7-b05f-4763-bf75-10b8d4cfc7c7@mailbox.org> (raw)
In-Reply-To: <20251120155401.GI2125796@bill-the-cat>

On 11/20/25 4:54 PM, Tom Rini wrote:

Hello Tom,

>>>>> , and then
>>>>> every follow-up location doesn't need to perform that (or possibly many
>>>>> other as well) validation checks. My impression from when I looked at
>>>>> the code last, a few year ago, was that it was designed with "validate
>>>>> with most? every? function" and we would be happy enough with "validate
>>>>> once".
>>>>
>>>> If you can make that assumption -- that whatever we feed into libfdt is
>>>> valid -- then we can simply patch out can_assume() .
>>>
>>> Maybe the question I have then is, why isn't can_assume being optimized
>>> out at compile time, if we set the mask right. Makes me wonder if
>>> there's not something to fix upstream too. Or maybe we need to change
>>> the default to higher than 0?
>>
>> Maybe because the mask is set differently for U-Boot and SPL , see:
>>
>> CONFIG_SPL_OF_LIBFDT_ASSUME_MASK=0xff
>> CONFIG_OF_LIBFDT_ASSUME_MASK=0x0
> 
> Right. We might want a different default for full U-Boot at this point
> (not assume perfect, but also not assume nothing).

For SPL, we assume perfect. For U-Boot, we assume not valid at all.

I think this configuration is actually what we want, keep SPL size 
small, perform validation of DT in U-Boot because it might come from a 
command line.

> But still, I would
> have hoped SPL growth was smaller, but perhaps I just need to
> re-evaluate things. Let me know when you have a next iteration of
> everything branch somewhere and I'll run the size growth build before
> you post if you like and we can iterate on it.
The latest is always in u-boot-sh / test-dtc branch.

  reply	other threads:[~2025-11-20 20:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 12:21 [PATCH 0/3] Synchronize DTC to 1.7.2 Marek Vasut
2025-11-13 12:21 ` [PATCH 1/3] dm: core: Check ofnode_to_offset() return value Marek Vasut
2025-11-13 19:33   ` Simon Glass
2025-11-13 21:51     ` Marek Vasut
2025-11-13 22:46       ` Simon Glass
2025-11-14  5:17         ` Marek Vasut
2025-11-14 14:36           ` Tom Rini
2025-11-16  0:16             ` Marek Vasut
2025-11-16 14:13               ` Tom Rini
2025-11-16 21:28                 ` Marek Vasut
2025-11-17 14:14                   ` Tom Rini
2025-11-13 12:21 ` [PATCH 2/3] scripts/dtc: Update to upstream version v1.7.2-35-g52f07dcca47c Marek Vasut
2025-11-13 12:21 ` [PATCH 3/3] libfdt: Check fdt_offset_ptr() return value unconditionally Marek Vasut
2025-11-13 19:33   ` Simon Glass
2025-11-13 21:48     ` Marek Vasut
2025-11-13 23:34       ` Simon Glass
2025-11-20  4:20         ` Marek Vasut
2025-11-13 17:57 ` [PATCH 0/3] Synchronize DTC to 1.7.2 Tom Rini
2025-11-13 18:40   ` Marek Vasut
2025-11-13 18:49     ` Tom Rini
2025-11-13 19:32       ` Simon Glass
2025-11-15 23:23       ` Marek Vasut
2025-11-16 14:11         ` Tom Rini
2025-11-16 21:48           ` Marek Vasut
2025-11-17 18:40             ` Tom Rini
2025-11-19 21:31               ` Marek Vasut
2025-11-20 15:54                 ` Tom Rini
2025-11-20 20:14                   ` Marek Vasut [this message]
2025-11-21 19:55   ` Tom Rini
2025-12-02 17:46     ` Marek Vasut
2025-12-02 18:06       ` Tom Rini
2025-12-02 18:35         ` Marek Vasut

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=49969be7-b05f-4763-bf75-10b8d4cfc7c7@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=adrianox@gmail.com \
    --cc=andrew.goodbody@linaro.org \
    --cc=ansuelsmth@gmail.com \
    --cc=cfsworks@gmail.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=patrice.chotard@foss.st.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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