public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr
Date: Wed, 02 Mar 2011 03:54:53 +0100	[thread overview]
Message-ID: <4D6DB17D.7010601@ahsoftware.de> (raw)
In-Reply-To: <1299022621-2780-1-git-send-email-jkridner@beagleboard.org>

Hello Jason,

On 02.03.2011 00:37, Jason Kridner wrote:

> From: Alexander Holler<holler@ahsoftware.de>
>
> Using the new env import command it is possible to use plain text files instead
> of script-images. Plain text files are much easier to handle.
>
> E.g. If your boot.scr contains the following:
> -----------------------------------
> setenv dvimode 1024x768-16 at 60
> run loaduimage
> run mmcboot
> -----------------------------------
> you could create a file named uEnv.txt and use that instead of boot.scr:
> -----------------------------------
> dvimode=1024x768-16 at 60
> uenvcmd=run loaduimage; run mmcboot
> -----------------------------------
> The variable uenvcmd (if existent) will be executed (using run) after uEnv.txt
> was loaded. If uenvcmd doesn't exist the default boot sequence will be started,
> therefore you could just use
> -----------------------------------
> dvimode=1024x768-16 at 60
> -----------------------------------
> as uEnv.txt because loaduimage and mmcboot is part of the default boot sequence.
>
> For backwards compatibility the use of boot.scr is still supported.
> ---
> Changes for v2:
>    - Eliminated else redundant clause that would be ignored if boot
>      succeeds.


If I interpret your change correctly, your v2 would use uEnv.txt and 
boot.scr if both are existent. I think this would only lead to confusion.
My target was to get rid of boot.scr and to therefor boot.scr would be 
ignored if uEnv.txt exists. I don't see any reason why boot.scr should 
be still used when uEnv.txt exists.


>
> Signed-off-by: Jason Kridner<jkridner@beagleboard.org>
> Cc: Alexander Holler<holler@ahsoftware.de>
> ---
>   include/configs/omap3_beagle.h |   26 ++++++++++++++++++--------
>   1 files changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h
> index f151e98..b7f5480 100644
> --- a/include/configs/omap3_beagle.h
> +++ b/include/configs/omap3_beagle.h
> @@ -229,6 +229,9 @@
>   	"loadbootscript=fatload mmc ${mmcdev} ${loadaddr} boot.scr\0" \
>   	"bootscript=echo Running bootscript from mmc ...; " \
>   		"source ${loadaddr}\0" \
> +	"loadbootenv=fatload mmc ${mmcdev} ${loadaddr} uEnv.txt\0" \
> +	"importbootenv=echo Importing environment from mmc ...; " \
> +		"env import -t $loadaddr $filesize\0" \
>   	"loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage\0" \
>   	"mmcboot=echo Booting from mmc ...; " \
>   		"run mmcargs; " \
> @@ -240,15 +243,22 @@
>
>   #define CONFIG_BOOTCOMMAND \
>   	"if mmc rescan ${mmcdev}; then " \
> +		"echo SD/MMC found on device ${mmcdev};" \
> +		"if run loadbootenv; then " \
> +			"run importbootenv;" \
> +		"fi;" \
> +		"if test -n $uenvcmd; then " \
> +			"echo Running uenvcmd ...;" \
> +			"run uenvcmd;" \
> +		"fi;" \
>   		"if run loadbootscript; then " \
> -			"run bootscript; " \
> -		"else " \
> -			"if run loaduimage; then " \
> -				"run mmcboot; " \
> -			"else run nandboot; " \
> -			"fi; " \
> -		"fi; " \
> -	"else run nandboot; fi"
> +			"run bootscript;" \
> +		"fi;" \
> +		"if run loaduimage; then " \
> +			"run mmcboot;" \
> +		"fi;" \
> +	"fi;" \
> +	"run nandboot;" \
>
>   #define CONFIG_AUTO_COMPLETE		1
>   /*

Regards,

Alexander

  reply	other threads:[~2011-03-02  2:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 23:08 [U-Boot] [PATCH] omap3_beagle: enable the use of a plain text file named uEnv.txt instead of boot.scr Alexander Holler
2011-02-04 17:41 ` Jason Kridner
2011-03-01 23:37 ` [U-Boot] [PATCH v2] " Jason Kridner
2011-03-02  2:54   ` Alexander Holler [this message]
2011-03-02 15:44     ` Jason Kridner
2011-03-02 17:47       ` Alexander Holler
2011-03-02 19:55         ` Alexander Holler
2011-03-02 20:26   ` [U-Boot] [PATCH v3] " Jason Kridner
2011-03-02 23:41     ` Alexander Holler
2011-03-02 23:48       ` [U-Boot] [beagleboard] " Robert Nelson
2011-03-03 15:04         ` Jason Kridner
2011-03-04  1:30           ` Alexander Holler
2011-03-04  1:43         ` [U-Boot] " Alexander Holler
2011-03-04  1:51           ` Robert Nelson
2011-03-03 15:08     ` [U-Boot] [PATCH v4] " Jason Kridner
2011-03-05 12:31       ` Alexander Holler
2011-03-05 12:50         ` Alexander Holler
2011-03-13 21:26         ` Wolfgang Denk
2011-04-18 21:35     ` [U-Boot] [PATCH v3] " Paulraj, Sandeep
2011-04-18 23:01       ` Wolfgang Denk
2011-04-18 23:32         ` Paulraj, Sandeep

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=4D6DB17D.7010601@ahsoftware.de \
    --to=holler@ahsoftware.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