From: Denys Dmytriyenko <denis@denix.org>
To: Alistair Francis <Alistair.Francis@wdc.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"alistair23@gmail.com" <alistair23@gmail.com>,
"denys@ti.com" <denys@ti.com>
Subject: Re: [meta-yocto-bsp][PATCH] beaglebone-yocto: Update u-boot config to match u-boot 19.04
Date: Thu, 11 Apr 2019 14:06:38 -0400 [thread overview]
Message-ID: <20190411180638.GP2112@denix.org> (raw)
In-Reply-To: <20190411172609.16625-1-alistair.francis@wdc.com>
On Thu, Apr 11, 2019 at 05:27:25PM +0000, Alistair Francis wrote:
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Acked-by: Denys Dmytriyenko <denys@ti.com>
[YOCTO #13145]
This was announced at 2019.01:
https://www.mail-archive.com/u-boot@lists.denx.de/msg305424.html
Basically, am335x_boneblack is just a special subset of am335x_evm config,
created and owned by BeagleBoard.org community. Since it was not migrated to
use CONFIG_BLK in time for 2019.04 release, I was going to do the same - just
switch it over to am335x_evm config, which supports all BeagleBone variants
just fine.
> ---
> meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> index 70d3cfe..bc18ee8 100644
> --- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> +++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> @@ -32,7 +32,7 @@ KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
>
> SPL_BINARY = "MLO"
> UBOOT_SUFFIX = "img"
> -UBOOT_MACHINE = "am335x_boneblack_config"
> +UBOOT_MACHINE = "am335x_evm_defconfig"
> UBOOT_ENTRYPOINT = "0x80008000"
> UBOOT_LOADADDRESS = "0x80008000"
>
> --
> 2.21.0
>
prev parent reply other threads:[~2019-04-11 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 17:27 [meta-yocto-bsp][PATCH] beaglebone-yocto: Update u-boot config to match u-boot 19.04 Alistair Francis
2019-04-11 18:06 ` Denys Dmytriyenko [this message]
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=20190411180638.GP2112@denix.org \
--to=denis@denix.org \
--cc=Alistair.Francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=denys@ti.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.