From: Ralph Siemsen <ralph.siemsen@linaro.org>
To: Marek Vasut <marek.vasut@mailbox.org>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH v4 10/10] doc: renesas: add Renesas board docs
Date: Mon, 17 Apr 2023 16:29:35 -0400 [thread overview]
Message-ID: <20230417202935.GH642444@maple.netwinder.org> (raw)
In-Reply-To: <f4b7d0cb-384d-83e9-d2c3-f95baa41a283@mailbox.org>
On Mon, Apr 17, 2023 at 07:28:05PM +0200, Marek Vasut wrote:
>On 3/8/23 21:26, Ralph Siemsen wrote:
>RZ/N1
>
>>+ - Schneider rzn1-snarc board
>>+
>>+Building
>>+--------
>>+
>>+NOTE: the following information is for the rzn1 board only.
>
>Maybe this should be in a separate document , some rzn1 specific .rst file ?
Originally I did just document the RZ/N1 stuff, since I really have no
experience or knowledge of the other ones. But it felt wrong to create
"doc/board/renesas" containing only RZ/N1 information. So I tried to at
least collect the names of the other Renesas boards from U-Boot sources.
I'll make the fixes you suggested, and will move the RZ/N1 details into
their own file.
>>+ tools/mkimage -n board/schneider/rzn1-snarc/spkgimage.cfg \
>>+ -T spkgimage -a 0x20040000 -e 0x20040000 \
>>+ -d u-boot.bin u-boot.bin.spkg
>
>Shouldn't binman do this for you ? That should be the primary option.
Indeed it does, see below. I did however want to document how to call
mkimage manually, since it took me a while to work out the right
arguments (especially using -n for the config file).
>>+Binman
>>+^^^^^^
>>+
>>+Alternatively `binman` may be used to generate the SPKG format for booting.
>>+This tool and its pre-requisites must be installed as per
>>+:doc:`../../../tools/binman/binman.rst``
>>+
>>+.. code-block:: bash
>>+
>>+ binman -d arch/arm/dts/r9a06g032-rzn1-snarc.dtb -o <OUT>
>>+
>>+This will produce `u-boot.bin.spkg` in the specified <OUT> directory.
Ralph
next prev parent reply other threads:[~2023-04-17 20:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 20:26 [PATCH v4 00/10] Renesas RZ/N1 SoC initial support Ralph Siemsen
2023-03-08 20:26 ` [PATCH v4 01/10] ARM: armv7: add non-SPL enable for Cortex SMPEN Ralph Siemsen
2023-04-17 17:04 ` Marek Vasut
2023-04-17 18:26 ` Ralph Siemsen
2023-04-17 20:21 ` Marek Vasut
2023-04-18 14:32 ` Ralph Siemsen
2023-04-18 19:35 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 02/10] clk: renesas: prepare for non-RCAR clock drivers Ralph Siemsen
2023-04-17 17:02 ` Marek Vasut
2023-04-17 18:22 ` Ralph Siemsen
2023-04-17 20:33 ` Marek Vasut
2023-04-17 20:48 ` Ralph Siemsen
2023-04-17 22:24 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 03/10] clk: renesas: add R906G032 driver Ralph Siemsen
2023-04-17 17:07 ` Marek Vasut
2023-04-17 18:29 ` Ralph Siemsen
2023-03-08 20:26 ` [PATCH v4 04/10] pinctrl: " Ralph Siemsen
2023-04-17 17:09 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 05/10] ram: cadence: add driver for Cadence EDAC Ralph Siemsen
2023-04-17 17:32 ` Marek Vasut
2023-04-17 20:33 ` Ralph Siemsen
2023-03-08 20:26 ` [PATCH v4 06/10] dts: basic devicetree for Renesas RZ/N1 SoC Ralph Siemsen
2023-04-17 17:12 ` Marek Vasut
2023-04-17 18:33 ` Ralph Siemsen
2023-04-17 20:22 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 07/10] ARM: rzn1: basic support " Ralph Siemsen
2023-04-17 17:15 ` Marek Vasut
2023-04-17 18:57 ` Ralph Siemsen
2023-04-17 20:30 ` Marek Vasut
2023-04-17 20:44 ` Ralph Siemsen
2023-04-17 22:23 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 08/10] board: schneider: add RZN1 board support Ralph Siemsen
2023-04-17 17:18 ` Marek Vasut
2023-04-17 19:45 ` Ralph Siemsen
2023-04-17 20:27 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 09/10] tools: spkgimage: add Renesas SPKG format Ralph Siemsen
2023-04-17 17:23 ` Marek Vasut
2023-04-17 20:17 ` Ralph Siemsen
2023-04-17 20:28 ` Marek Vasut
2023-03-08 20:26 ` [PATCH v4 10/10] doc: renesas: add Renesas board docs Ralph Siemsen
2023-04-17 17:28 ` Marek Vasut
2023-04-17 20:29 ` Ralph Siemsen [this message]
2023-04-17 20:34 ` Marek Vasut
2023-04-17 20:50 ` Ralph Siemsen
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=20230417202935.GH642444@maple.netwinder.org \
--to=ralph.siemsen@linaro.org \
--cc=marek.vasut@mailbox.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