mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/4] of: fdt: read blspec/FIT DT compat without unflattening
Date: Mon, 04 Mar 2024 10:49:27 +0100	[thread overview]
Message-ID: <170954576784.2746656.14484773738845201870.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240301130445.171385-1-a.fatoum@pengutronix.de>


On Fri, 01 Mar 2024 14:04:41 +0100, Ahmad Fatoum wrote:
> blspec and FIT systems usually have multiple entries/configurations,
> where a suitable one should be selected at runtime by comparing each
> against the board's barebox DT compatible.
> 
> For blspec, this meant we need to unflatten the whole DT only to access
> a single property. For FIT, this meant we expected the configuration to
> carry a "compatible" property and didn't even attempt to parse it out of
> the fdt as fallback. Both are resolved with this series.
> 
> [...]

Applied, thanks!

[1/4] of: fdt: factor out FDT header parsing
      https://git.pengutronix.de/cgit/barebox/commit/?id=a8b58bf5d7cd (link may not be stable)
[2/4] of: fdt: implement fdt_machine_is_compatible
      https://git.pengutronix.de/cgit/barebox/commit/?id=143f2ae76809 (link may not be stable)
[3/4] blspec: don't parse whole device tree to compare compatibles
      https://git.pengutronix.de/cgit/barebox/commit/?id=9f2b74f1eb58 (link may not be stable)
[4/4] FIT: support finding compatible configuration by FDT compatible
      https://git.pengutronix.de/cgit/barebox/commit/?id=5c9cd335e893 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2024-03-04 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 13:04 Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 1/4] of: fdt: factor out FDT header parsing Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 2/4] of: fdt: implement fdt_machine_is_compatible Ahmad Fatoum
2024-03-04  9:37   ` Sascha Hauer
2024-03-04  9:49     ` Sascha Hauer
2024-03-04  9:50     ` Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 3/4] blspec: don't parse whole device tree to compare compatibles Ahmad Fatoum
2024-03-01 13:04 ` [PATCH 4/4] FIT: support finding compatible configuration by FDT compatible Ahmad Fatoum
2024-03-04  9:49 ` Sascha Hauer [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=170954576784.2746656.14484773738845201870.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox