All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Eric Schikschneit <eric.schikschneit@novatechautomation.com>
Cc: Simon Glass <sjg@chromium.org>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: [PATCH] [RFC]: dtc: Add Kconfig option to pad device tree blob
Date: Tue, 6 May 2025 10:58:00 -0600	[thread overview]
Message-ID: <20250506165800.GC5430@bill-the-cat> (raw)
In-Reply-To: <SJ2PR07MB9711B7D339A7C25641310B018189A@SJ2PR07MB9711.namprd07.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

On Tue, May 06, 2025 at 12:49:55PM +0000, Eric Schikschneit wrote:

> Hello Tom,
> 
> The link that Simon sent does not add padding at the end. I have tried
> the approach with SYS_FDT_PAD first and my platform (imx6) still has
> issues when trying to modify the device tree from the board file. It
> still returns FDT_ERR_NOSPACE with that option. The commit I sent
> simply adds a Kconfig option to something we are already doing
> (passing the -p flag) on multiple platforms behind the scenes to the
> device tree compiler. I have tested and proven on my platform that
> this allows live modification of the device tree in the board file.

Ah, that's a good data point, thanks. Simon has a good follow-up
question about fdt_high being set to 0xffffffff and that being the root
cause (and so, undo that) being the other solution. And then in turn it
perhaps being past time for me to forcefully undo that on the boards
that snuck in that setting ages ago.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2025-05-06 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 18:38 [PATCH] [RFC]: dtc: Add Kconfig option to pad device tree blob Eric Schikschneit
2025-05-03  2:10 ` Simon Glass
2025-05-05 18:09   ` Tom Rini
2025-05-06 12:49     ` Eric Schikschneit
2025-05-06 13:24       ` Simon Glass
2025-05-06 16:58       ` Tom Rini [this message]
2025-05-16 16:28 ` Tom Rini
2025-05-19 14:58   ` Eric Schikschneit
2025-05-19 15:00     ` 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=20250506165800.GC5430@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=eric.schikschneit@novatechautomation.com \
    --cc=sjg@chromium.org \
    --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 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.