From: Ferry Toth <ftoth@telfort.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 2/2] x86: edison: Switch to CONFIG_OF_SEPARATE
Date: Thu, 10 Jan 2019 11:14:23 +0100 [thread overview]
Message-ID: <q175ps$nrn$1@blaine.gmane.org> (raw)
In-Reply-To: <20190108141743.20855-2-andriy.shevchenko@linux.intel.com>
Op 08-01-19 om 15:17 schreef Andy Shevchenko:
> There is no need for Intel Edison to have CONFIG_OF_EMBED to be enabled.
> Replace it with CONFIG_OF_SEPARATE.
>
> There is no functional change since u-boot.bin always contains DTB
> either embedded or attached.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Tested-by: Ferry Toth <ftoth@exalondelft.nl>
> ---
> configs/edison_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configs/edison_defconfig b/configs/edison_defconfig
> index e376c0cea6..dc7d86aafe 100644
> --- a/configs/edison_defconfig
> +++ b/configs/edison_defconfig
> @@ -26,7 +26,7 @@ CONFIG_CMD_EXT4=y
> CONFIG_CMD_EXT4_WRITE=y
> CONFIG_CMD_FAT=y
> CONFIG_CMD_FS_GENERIC=y
> -CONFIG_OF_EMBED=y
> +CONFIG_OF_SEPARATE=y
> CONFIG_DEFAULT_DEVICE_TREE="edison"
> CONFIG_ENV_IS_IN_MMC=y
> CONFIG_CPU=y
>
next prev parent reply other threads:[~2019-01-10 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 14:17 [U-Boot] [PATCH v1 1/2] doc: Fix CONFIG_OF_SEPARATE description Andy Shevchenko
2019-01-08 14:17 ` [U-Boot] [PATCH v1 2/2] x86: edison: Switch to CONFIG_OF_SEPARATE Andy Shevchenko
2019-01-10 10:14 ` Ferry Toth [this message]
2019-01-10 12:57 ` Simon Glass
2019-01-10 21:48 ` Ferry Toth
2019-01-31 7:38 ` Bin Meng
2019-01-10 12:56 ` [U-Boot] [PATCH v1 1/2] doc: Fix CONFIG_OF_SEPARATE description Simon Glass
2019-01-30 19:54 ` Andy Shevchenko
2019-01-31 7:38 ` Bin Meng
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='q175ps$nrn$1@blaine.gmane.org' \
--to=ftoth@telfort.nl \
--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