From: See, Chin Liang <chin.liang.see@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] ARM: socfpga: stratix10: Remove CONFIG_OF_EMBED
Date: Tue, 4 Jun 2019 05:58:05 +0000 [thread overview]
Message-ID: <1559627882.41120.9.camel@intel.com> (raw)
In-Reply-To: <CAAh8qsyfmM4nDEhKGBJ4vKtdyVoPxaVShXHEfb5Q22CVSvcpVA@mail.gmail.com>
On Tue, 2019-06-04 at 07:13 +0200, Simon Goldschmidt wrote:
> On Tue, Jun 4, 2019 at 1:57 AM Dalon Westergreen
> <dalon.westergreen@linux.intel.com> wrote:
> >
> >
> > From: Dalon Westergreen <dalon.westergreen@intel.com>
> >
> > CONFIG_OF_EMBED was primarily enabled to support the stratix10
> > spl hex file requirements. Since this option now produces a
> > warning during build, and the spl hex can be created using
> > alternate methods, CONFIG_OF_EMBED is no longer needed.
> >
> > Signed-off-by: Dalon Westergreen <dalon.westergreen@intel.com>
> >
> > ---
> > Changes in v2:
> > -> Change CONFIG_SPL_TARGET back to u-boot-spl.hex
> > ---
> > configs/socfpga_stratix10_defconfig | 1 -
> > include/configs/socfpga_stratix10_socdk.h | 2 +-
> > 2 files changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/configs/socfpga_stratix10_defconfig
> > b/configs/socfpga_stratix10_defconfig
> > index fbab388b43..f27180385d 100644
> > --- a/configs/socfpga_stratix10_defconfig
> > +++ b/configs/socfpga_stratix10_defconfig
> > @@ -26,7 +26,6 @@ CONFIG_CMD_CACHE=y
> > CONFIG_CMD_EXT4=y
> > CONFIG_CMD_FAT=y
> > CONFIG_CMD_FS_GENERIC=y
> > -CONFIG_OF_EMBED=y
> > CONFIG_DEFAULT_DEVICE_TREE="socfpga_stratix10_socdk"
> > CONFIG_ENV_IS_IN_MMC=y
> > CONFIG_NET_RANDOM_ETHADDR=y
> > diff --git a/include/configs/socfpga_stratix10_socdk.h
> > b/include/configs/socfpga_stratix10_socdk.h
> > index 39d757d737..66855ff0d8 100644
> > --- a/include/configs/socfpga_stratix10_socdk.h
> > +++ b/include/configs/socfpga_stratix10_socdk.h
> > @@ -210,6 +210,6 @@ unsigned int cm_get_l4_sys_free_clk_hz(void);
> >
> > /* SPL SDMMC boot support */
> > #define CONFIG_SYS_MMCSD_FS_BOOT_PARTITION 1
> > -#define CONFIG_SPL_FS_LOAD_PAYLOAD_NAME "u-
> > boot.img"
> > +#define CONFIG_SPL_FS_LOAD_PAYLOAD_NAME "u-boot-
> > dtb.img"
> Is that really necessary? I don't have the aarch64 compiler at hand,
> but when compiling a gen5 board, "u-boot.img" and "u-boot-dtb.img"
> are the same. Changing to "u-boot-dtb.img" here only complicates
> things for the user, I think.
I would agree with Dalon since we want to make sure we use same name as
socfpga_common.h, which is for CV, A10 SoCs. This would help to
standardize our internal test infra.
Thanks
Chin Liang
>
> Regards,
> Simon
>
> >
> >
> > #endif /* __CONFIG_H */
> > --
> > 2.21.0
> >
next prev parent reply other threads:[~2019-06-04 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 23:57 [U-Boot] [PATCH v2 1/2] Makefile: Add target to generate hex output for combined spl and dtb Dalon Westergreen
2019-06-03 23:57 ` [U-Boot] [PATCH v2 2/2] ARM: socfpga: stratix10: Remove CONFIG_OF_EMBED Dalon Westergreen
2019-06-04 5:13 ` Simon Goldschmidt
2019-06-04 5:58 ` See, Chin Liang [this message]
2019-06-04 6:12 ` Simon Goldschmidt
2019-06-04 16:10 ` Dalon L Westergreen
2019-06-04 18:15 ` Tom Rini
2019-06-04 18:34 ` Simon Goldschmidt
2019-06-04 0:00 ` [U-Boot] [PATCH v2 1/2] Makefile: Add target to generate hex output for combined spl and dtb Marek Vasut
2019-06-04 3:12 ` Dalon L Westergreen
2019-06-04 11:20 ` Marek Vasut
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=1559627882.41120.9.camel@intel.com \
--to=chin.liang.see@intel.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