From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC 4/4] paz00: enable bootmenu
Date: Tue, 17 Mar 2015 09:14:50 -0600 [thread overview]
Message-ID: <550844EA.2080800@wwwdotorg.org> (raw)
In-Reply-To: <5507DEC1.30707@mail.ru>
On 03/17/2015 01:58 AM, Andrey Danin wrote:
> On 16.03.2015 21:14, Stephen Warren wrote:
>> On 03/13/2015 04:49 PM, Andrey Danin wrote:
>>> Signed-off-by: Andrey Danin <danindrey@mail.ru>
>>
>> Some explanation of what these new options do might be nice; the
>> features/benefits they enable.
>>
>> Are any of the options generally useful? If so, should they be enabled
>> in tegra-common*.h?
>>
>> You also didn't Cc Tom Warren (Tegra maintainer) so he likely won't see
>> the emails and hence won't apply this patch.
>
> Thanks for the reply Stephen! I will add Tom Warren to Cc next time.
>
>
> Bootmenu allows to create user friendly menu to choose different boot
> options. For example next 3 lines in boot config
> ---
> setenv bootmenu_0 "Boot kernel = setenv bootargs ..."
> setenv bootmenu_1 "Boot recovery = setenv bootargs ..."
> bootmenu 20
> ---
> will generate bootmenu with 3 options:
> ---
> *** U-Boot Boot Menu ***
>
> Boot kernel
> Boot recovery
> U-Boot console
>
>
> Press UP/DOWN to move, ENTER to select
> ---
>
> More information about bootmenu is available at doc/README.bootmenu
OK. Might it be better to use an extlinux.conf file? It already has
support for displaying a menu for all the options in the file, and
allowing the user to select which to boot. (Although I suspect the
extlinux.conf menu could be prettied up some). I suppose your example
above are more than just selecting which kernel to boot though, so
perhaps extlinux.conf wouldn't work.
> I was focused on console part for this RFC. This patch is for testing
> purposes. I will use tegra config instead of paz00 next time to allow
> other users of tegra devices to try changes.
next prev parent reply other threads:[~2015-03-17 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 22:49 [U-Boot] [RFC 0/4] ansi console support for lcd driver Andrey Danin
2015-03-13 22:49 ` [U-Boot] [RFC 1/4] common: add ansi console base implementation Andrey Danin
2015-03-18 13:06 ` Nikita Kiryanov
2015-03-13 22:49 ` [U-Boot] [RFC 2/4] video: cfb_console: use common ansi implementation Andrey Danin
2015-03-13 22:49 ` [U-Boot] [RFC 3/4] lcd: use ansi console Andrey Danin
2015-03-13 22:49 ` [U-Boot] [RFC 4/4] paz00: enable bootmenu Andrey Danin
2015-03-16 18:14 ` Stephen Warren
2015-03-17 7:58 ` Andrey Danin
2015-03-17 15:14 ` Stephen Warren [this message]
2015-03-18 12:58 ` [U-Boot] [RFC 0/4] ansi console support for lcd driver Nikita Kiryanov
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=550844EA.2080800@wwwdotorg.org \
--to=swarren@wwwdotorg.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