From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Kconfig: add CONFIG_CMD_BOOTZ
Date: Mon, 12 Oct 2015 21:48:20 +0300 [thread overview]
Message-ID: <561C0074.40801@compulab.co.il> (raw)
In-Reply-To: <CAPnjgZ24d7YOub3+wQCwL5qGtwA351mmZKKp5wHp7_XG-V6=GQ@mail.gmail.com>
Hi Simon,
On 10/09/15 12:36, Simon Glass wrote:
> Hi Igor,
>
> On 8 October 2015 at 19:48, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> Add CONFIG_CMD_BOOTZ to the Kconfig.
>> Since the CONFIG_CMD_BOOTZ cannot live without the CONFIG_CMD_BOOTM,
>> make it select the CONFIG_CMD_BOOTM.
>>
>> Signed-off-by: Igor Grinberg <grinberg@compulab.co.il>
>> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
>> Cc: Simon Glass <sjg@chromium.org>
>> ---
>> common/Kconfig | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/common/Kconfig b/common/Kconfig
>> index 2c42b8e..d98eb19 100644
>> --- a/common/Kconfig
>> +++ b/common/Kconfig
>> @@ -148,6 +148,12 @@ config CMD_BOOTM
>> help
>> Boot an application image from the memory.
>>
>> +config CMD_BOOTZ
>> + bool "bootz"
>> + select CMD_BOOTM
>
> Do we need this, or can it be 'depends on CMD_BOOTM'?
Well, the way I see it is that today (with the multi-platform support
in the kernel) you do not need the bootm command (historically happened
that it represents the uImage) and you just want the bootz command.
If we make it "depend" on bootm, the bootz entry will not show up until
you enable the bootm command. That might be not trivial for the "regular"
user who just want to adjust the configuration and build a new binary...
Well of course it can be argued, but I really like how it works with
"select" and I see bootz as an independent command and technically it
happens that they share the same code for the most of it.
>
>> + help
>> + Boot a Linux kernel zImage from the memory.
>> +
>
> Could you add a brief description of what a zImage is and how it gets
> created? It would be good to be a bit more descriptive in these help
> messages.
Yes that is a great idea, and of course it went through my head, but
the problem is that I'm completely out of time and I've seen the other
commands have that simple one liners, so I just did the same thing.
I will try to figure out something more descriptive, but I'm "overbooked"
with work (I've actually used my conferences time to prepare/send the
patches).
>
>> config CMD_GO
>> bool "go"
>> default y
>> --
>> 2.4.9
>>
>
> Regards,
> Simon
>
--
Regards,
Igor.
next prev parent reply other threads:[~2015-10-12 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 18:48 [U-Boot] [PATCH 0/2] config: move CONFIG_CMD_BOOTZ to defconfig Igor Grinberg
2015-10-08 18:48 ` [U-Boot] [PATCH 1/2] Kconfig: add CONFIG_CMD_BOOTZ Igor Grinberg
2015-10-09 9:36 ` Simon Glass
2015-10-12 18:48 ` Igor Grinberg [this message]
2015-10-08 18:48 ` [U-Boot] [PATCH 2/2] config: move CONFIG_CMD_BOOTZ to defconfig Igor Grinberg
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=561C0074.40801@compulab.co.il \
--to=grinberg@compulab.co.il \
--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