mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: "Sebastian Groß" <sebastian.gross@emlix.com>
Cc: barebox@lists.infradead.org, mainlining@emlix.com
Subject: Re: bootm: fit-image: hash node name too strict
Date: Tue, 7 Jan 2025 08:37:18 +0100	[thread overview]
Message-ID: <20250107073718.67626a7dq3afqjaz@pengutronix.de> (raw)
In-Reply-To: <92d4dd39-529d-4e4c-b231-76c3ba1790a7@emlix.com>

Hi Sebastian,

On 25-01-07, Sebastian Groß wrote:
> Hello and a happy new year 2025 dear all,

thank you very much, you too :)

> I happened to have a fit-image which worked fine with u-boot and wanted to
> give it a try with barebox.
> Sadly I got yelled at for not having hashes for the kernel-1 `Image`
> provided in the fit-image.
> 
> Grepping the source code for the error message pointed to `fit_verify_hash`
> and `of_get_child_by_name` with `hash@1` or `hash-1`.
> Neither is required by u-boot as it looks only for `FIT_HASH_NODENAME` which
> is defined as `hash`.

According the spec [1] it should be named hash-<number>. Checking the
U-Boot doc folder it seems like 'hash' was used in the early days of FIT
images since there is only one file 'doc/usage/fit/howto.rst' which is
using the plain 'hash' node name.

[1] https://fitspec.osfw.foundation/#hash-nodes

> Since the image is build by uboot's mkimage I would expect the itb's to be
> compatible. Or am I missing something?
> 
> Changing the following line in the `its`, ie. its build script
> ```
> - hash { algo = "${FIT_HASH_ALG}"; };
> + hash@1 { algo = "${FIT_HASH_ALG}"; };
> ```
> made the fit-image work.

I can't find this line within the U-Boot src code. Can you provide a
link please?

> Perhaps another if-clause is required. Or some error message that states
> which property/string was searched for,
> since there were hashes in the image, but not where barebox expected them.

We could search for the legacy single 'hash' node name as well and print
a warning that this should be changed.

Regards,
  Marco

> 
> Regards
> 
> Sebastian Groß
> 
> --
> Sebastian Groß, B.Sc.
> 
> emlix GmbH
> Headquarters: Berliner Str. 12, 37073 Goettingen, Germany
> Phone +49 (0)551 30664-0, e-mail info@emlix.com
> District Court of Goettingen, Registry Number HR B 3160
> Managing Directors: Heike Jordan, Dr. Uwe Kracke
> VAT ID No. DE 205 198 055
> Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
> Office Bonn: Bachstr. 6, 53115 Bonn, Germany
> http://www.emlix.com
> 
> emlix - your embedded Linux partner
> 
> 
> 



  reply	other threads:[~2025-01-07  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07  7:14 Sebastian Groß
2025-01-07  7:37 ` Marco Felsch [this message]
2025-01-07  7:54   ` Sebastian Groß
2025-01-07 11:13     ` Marco Felsch
2025-01-07 13:13       ` Sebastian Groß

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=20250107073718.67626a7dq3afqjaz@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mainlining@emlix.com \
    --cc=sebastian.gross@emlix.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