public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] omap4: duovero: Add Gumstix DuoVero machine.
Date: Tue, 6 May 2014 14:06:36 -0400	[thread overview]
Message-ID: <20140506180636.GW22182@bill-the-cat> (raw)
In-Reply-To: <1398807093-30788-1-git-send-email-ashcharles@gmail.com>

On Tue, Apr 29, 2014 at 02:31:33PM -0700, Ash Charles wrote:

> This adds the Gumstix DuoVero machine [1].  This is a OMAP4430-based
> computer-on-module (COM aka SOM) that can be mounted on various
> expansion boards with different peripherals.
[snip]
> +	gd->bd->bi_arch_number = MACH_TYPE_OMAP4_DUOVERO;

You don't really support non-DT kernels do you?

> +	gd->bd->bi_boot_params = (0x80000000 + 0x100); /* boot param addr */

CONFIG_SYS_SDRAM_BASE + ...

> diff --git a/include/configs/ti_omap4_common.h b/include/configs/ti_omap4_common.h
> index bcb5eab..4563cbb 100644
> --- a/include/configs/ti_omap4_common.h
> +++ b/include/configs/ti_omap4_common.h
> @@ -111,9 +111,13 @@
>  	"importbootenv=echo Importing environment from mmc${mmcdev} ...; " \
>  		"env import -t ${loadaddr} ${filesize}\0" \
>  	"loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}\0" \
> +	"loaduimage=fatload mmc ${mmcdev} ${loadaddr} uImage\0" \
>  	"mmcboot=echo Booting from mmc${mmcdev} ...; " \
>  		"run mmcargs; " \
>  		"bootz ${loadaddr} - ${fdtaddr}\0" \
> +	"uimageboot=echo Booting from mmc${mmcdev} ...; " \
> +		"run mmcargs; " \
> +		"bootm ${loadaddr}\0" \

First, please use 'load' not 'fatload' and second..

>  	"findfdt="\
>  		"if test $board_name = sdp4430; then " \
>  			"setenv fdtfile omap4-sdp.dtb; fi; " \
> @@ -123,6 +127,8 @@
>  			"setenv fdtfile omap4-panda-a4.dtb; fi;" \
>  		"if test $board_name = panda-es; then " \
>  			"setenv fdtfile omap4-panda-es.dtb; fi;" \
> +		"if test $board_name = duovero; then " \
> +			"setenv fdtfile omap4-duovero.dtb; fi;" \
>  		"if test $fdtfile = undefined; then " \
>  			"echo WARNING: Could not determine device tree to use; fi; \0" \
>  	"loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}\0" \
> @@ -146,6 +152,9 @@
>  			"run loadfdt;" \
>  			"run mmcboot; " \
>  		"fi; " \
> +		"if run loaduimage; then " \
> +			"run uimageboot;" \
> +		"fi; " \

You really are using uImage and not zImage for this board, but not for
pepper?

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140506/76aa1ff2/attachment.pgp>

  reply	other threads:[~2014-05-06 18:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 21:31 [U-Boot] [PATCH] omap4: duovero: Add Gumstix DuoVero machine Ash Charles
2014-05-06 18:06 ` Tom Rini [this message]
2014-05-07 16:01   ` Ash Charles
2014-05-07 16:02     ` [U-Boot] [PATCH v2] " Ash Charles
2014-05-13 23:44       ` Tom Rini

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=20140506180636.GW22182@bill-the-cat \
    --to=trini@ti.com \
    --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