From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dragonboard410c: Fix environment variables
Date: Wed, 13 Apr 2016 14:22:54 +0200 [thread overview]
Message-ID: <570E3A1E.4020102@suse.de> (raw)
In-Reply-To: <1460549782-25175-1-git-send-email-afaerber@suse.de>
Hi Daniel,
Am 13.04.2016 um 14:16 schrieb Andreas F?rber:
> Some variables for the distro boot commands were missing, using some
> custom name instead. Rename them.
>
> Cc: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
> Signed-off-by: Andreas F?rber <afaerber@suse.de>
> ---
> include/configs/dragonboard410c.h | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/include/configs/dragonboard410c.h b/include/configs/dragonboard410c.h
> index a63440f..6dd5fbf 100644
> --- a/include/configs/dragonboard410c.h
> +++ b/include/configs/dragonboard410c.h
> @@ -126,10 +126,10 @@ REFLASH(dragonboard/u-boot.img, 8)\
> "fdt_high=0xffffffffffffffff\0" \
> "initrd_high=0xffffffffffffffff\0" \
> "linux_image=Image\0" \
> - "linux_addr=0x81000000\0"\
> - "fdt_image=apq8016-sbc.dtb\0" \
> - "fdt_addr=0x83000000\0"\
> - "ramdisk_addr=0x84000000\0"\
> + "kernel_addr_r=0x81000000\0"\
> + "fdtfile=apq8016-sbc.dtb\0" \
> + "fdt_addr_r=0x83000000\0"\
> + "ramdisk_addr_r=0x84000000\0"\
> BOOTENV
>
> #define CONFIG_ENV_IS_NOWHERE
Forgot about investigating scriptaddr you mentioned. We can either add
it in a v2 if there's something else, or you can follow up after this.
EFI was still not working for me and I did not yet test boot.scr.
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2016-04-13 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:16 [U-Boot] [PATCH] dragonboard410c: Fix environment variables Andreas Färber
2016-04-13 12:22 ` Andreas Färber [this message]
2016-04-21 11:24 ` [U-Boot] " 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=570E3A1E.4020102@suse.de \
--to=afaerber@suse.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