public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH 1/4] mkimage: also honour -B even without external data
Date: Mon, 25 Sep 2023 10:47:17 +0200	[thread overview]
Message-ID: <b655aee9-ebc6-044a-cc7f-9e28d850b671@prevas.dk> (raw)
In-Reply-To: <CAPnjgZ09St0710SRLzubphauTYMtE1PyxAFWEKsupA2dAhXRbw@mail.gmail.com>

On 22/09/2023 17.26, Simon Glass wrote:

>>> Shouldn't this be fdt_open_into()?
>>
>> I honestly just copy-pasted fit_extract_data() and shaved it down to the
>> part that does the "align the FDT part of the file".
>>
>> I don't really understand your question. Are you saying this doesn't
>> work (or maybe doesn't work in some cases), or are you saying that
>> there's a simpler way to do this? For the latter, sure, one doesn't
>> really need to parse the whole FDT; we could just
>>
>>   open()
>>   pread() length from FDT header, convert to cpu-endianness
>>   length = ALIGN(length)
>>   pwrite() the new length in fdt-endianness
>>   ftruncate()
>>   close()
>>
>> but I thought it was better to stay closer to how fit_extract_data() was
>> done.
> 
> I mean that fdt_open_into() does more than just set the size (from
> what I can tell). But looking further I see other code which calls
> fdt_set_totalsize() so perhaps it is fine.

Yes, I think it's as it should be - as a I said, this is really just a
trimmed-down copy of the function which moves the data externally, and
also needs to make the size of the base fdt structure aligned.

Since patches 2,3,4 touch binman code, could you take all four?

Thanks,
Rasmus


  reply	other threads:[~2023-09-25  8:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 11:37 [PATCH 0/4] mkimage: also honour -B even without external data Rasmus Villemoes
2023-09-19 11:37 ` [PATCH 1/4] " Rasmus Villemoes
2023-09-21  1:02   ` Simon Glass
2023-09-21  7:57     ` Rasmus Villemoes
2023-09-22 15:26       ` Simon Glass
2023-09-25  8:47         ` Rasmus Villemoes [this message]
2023-09-25 13:10           ` Simon Glass
2023-09-25 13:25             ` Rasmus Villemoes
2023-09-27 19:02   ` Sean Anderson
2023-09-28  7:10     ` Rasmus Villemoes
2023-09-29 13:16       ` Sean Anderson
2023-11-04 19:43         ` Simon Glass
2023-11-06  8:15           ` Rasmus Villemoes
2023-09-19 11:37 ` [PATCH 2/4] binman: test: rename 275_fit_align.dts -> 275_fit_align_external.dts Rasmus Villemoes
2023-09-21  1:02   ` Simon Glass
2023-09-19 11:37 ` [PATCH 3/4] tools: binman: add test case for fit, align without fit, external-offset Rasmus Villemoes
2023-09-21  1:03   ` Simon Glass
2023-09-19 11:37 ` [PATCH 4/4] binman: update documentation for fit,align property Rasmus Villemoes
2023-09-21  1:03   ` Simon Glass
2023-09-25 15:14   ` Jonas Karlman
2023-09-26  6:25     ` Rasmus Villemoes
2023-09-27 14:19       ` Simon Glass
2023-09-28  8:02 ` [PATCH 5/4] mkimage: update man page and -h output Rasmus Villemoes
2023-10-02  1:17   ` Simon Glass
2023-10-11 18:37   ` Tom Rini
2023-10-11 19:07     ` Rasmus Villemoes
2023-10-11 19:33       ` Tom Rini
2023-10-12  2:40         ` Simon Glass
2023-10-12  2:17       ` Sean Anderson
2023-10-12 12:02         ` Tom Rini
2023-10-13 18:30         ` Rasmus Villemoes
2023-11-07  0:46           ` Sean Anderson
2023-11-07  7:30             ` Rasmus Villemoes
2023-11-07  7:33               ` Rasmus Villemoes

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=b655aee9-ebc6-044a-cc7f-9e28d850b671@prevas.dk \
    --to=rasmus.villemoes@prevas.dk \
    --cc=alpernebiyasak@gmail.com \
    --cc=kever.yang@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox