public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Johan Jonker <jbx6244@gmail.com>
Cc: Simon Glass <sjg@chromium.org>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Kever Yang <kever.yang@rock-chips.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Akash Gajjar <akash@openedev.com>,
	Jagan Teki <jagan@amarulasolutions.com>,
	Samuel Dionne-Riel <samuel@dionne-riel.com>,
	Andrew Abbott <andrew@mirx.dev>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [RFC PATCH 2/8] rockchip: Add binman definitions for final images
Date: Thu, 19 May 2022 14:35:01 +0300	[thread overview]
Message-ID: <852802e0-ec1e-2329-23f1-d75ddbc9df36@gmail.com> (raw)
In-Reply-To: <ac687eac-70cd-9950-2844-7e814222540b@gmail.com>

On 27/04/2022 12:22, Johan Jonker wrote:
> [...]
> 
> There's a trend to solve everything in python.
> Don't have knowledge about python, but there's a 3rd image format for
> NAND [1]. Could someone advise how to fit the extra XXX padding option
> in the mkimage.py file? (Simon ?)

Binman's mkimage support is mostly a wrapper around the mkimage
executable, so that patch would need to be applied first. Assuming you
want to run something like the example in that patch:

> mkimage -n rk3066 -T rknand -d <tpl>:<spl> -X 16384,1 <out>

I think you'd only need something like the first patch of this series
for binman to get the multiple inputs working, and I expect a binman dtb
fragment like the following would then work for the above command:

    mkimage {
        args = "-n", CONFIG_SYS_SOC, "-T", "rknand", "-X", "16384,1";

        u-boot-tpl {
        };

        u-boot-spl {
        };
    };

> Could someone from Rockchip give info on whether the SD or SPI image
> format has similarity to the NAND image format to reuse code? (Kever ?)
> 
> Missing are u-boot documents on Rockchip file formats itself other then
> reading the /tools/rkxxx.c code.

(I don't know the formats' details, so can't comment on those.)

> Currently there's a small section about rkimage, rksd and rkspi in
> README.rockchip. Move that to rockchip.rst as well when busy with image
> formats in this serie?
> 
> Johan
> 
> ===
> 
> [1]
> [PATCH v4 11/19] rockchip: mkimage: add support for rockchip nand boot image
> https://lore.kernel.org/u-boot/45576df80a77657cb2245ea1d1fc2e69908a909d.1502974488.git.paweljarosz3691@gmail.com/

  parent reply	other threads:[~2022-05-19 11:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  0:03 [RFC PATCH 0/8] Build Rockchip final images using binman Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 1/8] binman: mkimage: Support ':'-separated inputs Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 2/8] rockchip: Add binman definitions for final images Andrew Abbott
2022-04-27  9:22   ` Johan Jonker
2022-05-04  9:52     ` Andrew Abbott
2022-05-19 11:35     ` Alper Nebi Yasak [this message]
2022-04-25  0:03 ` [RFC PATCH 3/8] soc: rockchip: Include common U-Boot dtsi file Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 4/8] board: rockchip: Move SPI U-Boot offset to config Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 5/8] rockchip: Remove obsolete Makefile targets Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 6/8] rockchip: Enable binman for ARM64 Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 7/8] doc: rockchip: Update for new binman image generation Andrew Abbott
2022-04-25  0:03 ` [RFC PATCH 8/8] board: rockpro64: Enable building SPI image Andrew Abbott

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=852802e0-ec1e-2329-23f1-d75ddbc9df36@gmail.com \
    --to=alpernebiyasak@gmail.com \
    --cc=akash@openedev.com \
    --cc=andrew@mirx.dev \
    --cc=jagan@amarulasolutions.com \
    --cc=jbx6244@gmail.com \
    --cc=kever.yang@rock-chips.com \
    --cc=pbrobinson@gmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=samuel@dionne-riel.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