From: stefano babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/3] imx-common/cmd_resetmode.c: add imx resetmode command
Date: Thu, 09 Aug 2012 23:12:59 +0200 [thread overview]
Message-ID: <502427DB.1080401@denx.de> (raw)
In-Reply-To: <50240FA6.9040009@boundarydevices.com>
Am 09/08/2012 21:29, schrieb Eric Nelson:
>>> Why do you not pass the mode to do_resetmode_cmd() and let this function
>>> parse the argument, without these help functions ? Then we do not need
>>> to add new functions if we have, for example, mmc2 or mmc3.
>>
>> These functions are requested shortcuts.
>> "bootmmc0" is the same as "resetmode mmc0 && reset"
>>
> Hi Troy,
>
> As one of the few that made this request:
>
> I take it back...
>
> I was mostly after a single command that also performs 'reset',
> and agree with Stefano that an argument for the mode is a better
> implementation.
+1
>
> U-Boot> bootto usb
> U-Boot> bootto mmc
>
> I'm also rethinking the request for 'resetmode' because
> of the conflict with 'reset' (i.e. 'res' is no longer a
> unique command-complete).
Yes, there is no reason to have a conflict with "reset"
> The first implementation with
> 'rsmode' seemed to be an odd abbreviation.
>
> Anybody else have a suggestion?
>
> U-Boot> rstmode usb && reset
> U-Boot> bmode usb && reset
In Freescale documentation this is called "boot mode" - using the same
terminology can reduce confusion. I do not discuss which name is better,
but if someone reads the SOC's manual and then find a command for "boot
mode", it is normal that he automatically knows what is going on. "Boot"
conflicts with other u-boot command, then "bmode" is my first choice.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2012-08-09 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 1:26 [U-Boot] [PATCH V3 1/3] imx-common/cmd_resetmode.c: add imx resetmode command Troy Kisky
2012-08-09 1:26 ` [U-Boot] [PATCH V3 2/3] mx6qsabrelite: add resetmode support Troy Kisky
2012-08-09 1:26 ` [U-Boot] [PATCH V3 3/3] mx53evk: " Troy Kisky
2012-08-09 7:21 ` [U-Boot] [PATCH V3 1/3] imx-common/cmd_resetmode.c: add imx resetmode command Stefano Babic
2012-08-09 18:48 ` Troy Kisky
2012-08-09 19:29 ` Eric Nelson
2012-08-09 21:12 ` stefano babic [this message]
2012-08-09 21:49 ` Troy Kisky
2012-08-09 21:15 ` Troy Kisky
2012-08-10 1:09 ` Eric Nelson
2012-08-11 17:44 ` Stefano Babic
2012-08-09 20:05 ` stefano babic
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=502427DB.1080401@denx.de \
--to=sbabic@denx.de \
--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