From: "Andreas Färber" <afaerber@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] efi_loader: Fall back to fdtfile naming convention
Date: Thu, 14 Apr 2016 17:37:57 +0200 [thread overview]
Message-ID: <570FB955.6070500@suse.de> (raw)
In-Reply-To: <1460642874-241464-2-git-send-email-agraf@suse.de>
Am 14.04.2016 um 16:07 schrieb Alexander Graf:
> When there is no $fdtfile variable set, we still have a good chance
> that on 32bit arm the fdtfile really is just called $soc-$board.dtb.
>
> Enable the exports for $soc and $board in our distr defaults and make
"distro"
> use of them in the efi boot script.
>
> Reported-by: Andreas Faerber <afaerber@suse.de>
> Reported-by: Stephen Warren <swarren@wwwdotorg.org>
> Signed-off-by: Alexander Graf <agraf@suse.de>
>
> ---
>
> v1 -> v2:
>
> - set CONFIG_ENV_VARS_UBOOT_CONFIG instead of runtime config
> - s/efifdtfile/efi_fdtfile/g
Otherwise
Reviewed-by: Andreas F?rber <afaerber@suse.de>
ARM64 can be handled as follow-up.
Thanks,
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-14 15:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 14:07 [U-Boot] [PATCH v2 1/2] efi_loader: Pass fdt address directly to bootefi cmd Alexander Graf
2016-04-14 14:07 ` [U-Boot] [PATCH v2 2/2] efi_loader: Fall back to fdtfile naming convention Alexander Graf
2016-04-14 15:37 ` Andreas Färber [this message]
2016-04-21 11:25 ` [U-Boot] [U-Boot, v2, " Tom Rini
2016-04-14 15:29 ` [U-Boot] [PATCH v2 1/2] efi_loader: Pass fdt address directly to bootefi cmd Stephen Warren
2016-04-14 15:35 ` Andreas Färber
2016-04-14 17:55 ` Stephen Warren
2016-04-21 11:25 ` [U-Boot] [U-Boot, v2, " 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=570FB955.6070500@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