[OE-core] [PATCH] u-boot: update to 2015.01

[Denys Dmytriyenko]

On Wed, Jan 21, 2015 at 11:17:19AM -0200, Otavio Salvador wrote:
> On Tue, Jan 13, 2015 at 2:09 PM, Denys Dmytriyenko <denis at denix.org> wrote:
> > From: Denys Dmytriyenko <denys at ti.com>
> >
> > Signed-off-by: Denys Dmytriyenko <denys at ti.com>
> ...
> > +++ b/meta/recipes-bsp/u-boot/u-boot-fw-utils/0001-tools-env-fix-build-error.patch
> > @@ -0,0 +1,36 @@
> > +From ee2d75513452aa6d5306fd380104adc8a2f6d8f2 Mon Sep 17 00:00:00 2001
> > +From: Masahiro Yamada <yamada.m at jp.panasonic.com>
> > +Date: Wed, 3 Dec 2014 10:22:50 +0900
> > +Subject: [PATCH] tools: env: fix build error
> > +
> > +Since CONFIG_SYS_ARCH, CONFIG_SYS_CPU, ... were moved to Kconfig,
> > +tools/env/fw_printenv fails to build if CONFIG_ENV_VARS_UBOOT_CONFIG
> > +is defined.
> > +(I do not think this is the right way to fix the problem, but
> > +for now I do not have enough time to take a close look.)
> > +
> > +Upstream-Status: Submitted [http://patchwork.ozlabs.org/patch/417192/]
> > +
> > +Signed-off-by: Masahiro Yamada <yamada.m at jp.panasonic.com>
> > +Reported-by: Denys Dmytriyenko <denys at ti.com>
> 
> Is it necessary? In meta-fsl-arm we don't have this patch and get the
> tools built.

Really? The patch above is rather self-explanatory. The issue was confirmed by 
U-boot maintainers and the workaround provided by one of the core developers.
I'm not familiar with meta-fsl-arm, but I guess you can grep your platform's 
defconfig to see if CONFIG_ENV_VARS_UBOOT_CONFIG and others are defined and 
whether your platforms are affected or not. It does affect our platforms 
(among many others), including beaglebone.

-- 
Denys