From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Roman Stratiienko <r.stratiienko@gmail.com>
Cc: sjg@chromium.org, eajames@linux.ibm.com, xypron.glpk@gmx.de,
ilias.apalodimas@linaro.org, paulerwan.rio@gmail.com,
u-boot@lists.denx.de, igor.opaniuk@gmail.com
Subject: Re: [PATCH] abootimg: Add init_boot image support
Date: Thu, 23 May 2024 08:08:50 +0200 [thread overview]
Message-ID: <871q5tys99.fsf@baylibre.com> (raw)
In-Reply-To: <CAGphcd=ewtSE8VkfX=c4CL6-L7wj9badr3v_2Ep9QvJqHjZEiw@mail.gmail.com>
Hi Roman,
On jeu., mai 23, 2024 at 00:35, Roman Stratiienko <r.stratiienko@gmail.com> wrote:
[...]
>> >
>> > static struct cmd_tbl cmd_abootimg_sub[] = {
>> > - U_BOOT_CMD_MKENT(addr, 3, 1, do_abootimg_addr, "", ""),
>> > + U_BOOT_CMD_MKENT(addr, 4, 1, do_abootimg_addr, "", ""),
>> > U_BOOT_CMD_MKENT(dump, 2, 1, do_abootimg_dump, "", ""),
>> > U_BOOT_CMD_MKENT(get, 5, 1, do_abootimg_get, "", ""),
>> > U_BOOT_CMD_MKENT(load, 5, 1, do_abootimg_load, "", ""),
>> > @@ -375,7 +391,7 @@ static int do_abootimg(struct cmd_tbl *cmdtp, int flag, int argc,
>> > U_BOOT_CMD(
>> > abootimg, CONFIG_SYS_MAXARGS, 0, do_abootimg,
>> > "manipulate Android Boot Image",
>> > - "addr <boot_img_addr> [<vendor_boot_img_addr>]>\n"
>> > + "addr <boot_img_addr> [<vendor_boot_img_addr> [<init_boot_img_addr>]]\n"
>> > " - set the address in RAM where boot image is located\n"
>> > " ($loadaddr is used by default)\n"
>>
>> Please include the help text update in the documentation:
>> doc/android/boot-image.rst
>
> That documentation does not mention 'abootimg addr' command at the moment.
> I do not see an easy way to add it in a way that makes sense.
>
I see. I will send a documentation update later then.
>>
>> > "abootimg dump dtb\n"
>> > diff --git a/include/image.h b/include/image.h
>> > index be3c73a72e..b1fd6b3149 100644
[...]
prev parent reply other threads:[~2024-05-23 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 12:53 [PATCH] abootimg: Add init_boot image support Roman Stratiienko
2024-05-22 14:43 ` Mattijs Korpershoek
2024-05-22 21:35 ` Roman Stratiienko
2024-05-23 6:08 ` Mattijs Korpershoek [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=871q5tys99.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=eajames@linux.ibm.com \
--cc=igor.opaniuk@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=paulerwan.rio@gmail.com \
--cc=r.stratiienko@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.