Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Mon, Apr 30, 2018 at 9:25 PM Tom Rini wrote: > On Mon, Apr 30, 2018 at 08:29:56PM +, Otavio Salvador wrote: > > On Mon, Apr 30, 2018 at 5:25 PM Tom Rini wrote: > > We use our dtc-native. As we do for all other recipes (but few exceptions) > Then

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On April 30, 2018 7:25:10 PM GMT+02:00, Marek Vasut wrote: >On 04/30/2018 02:17 PM, Alexander Kanavin wrote: >> On 04/16/2018 11:40 AM, Marek Vasut wrote: Isn't it possible to solve your issue in the OE side? >>> >>> Can we NOT compile DTC alongside U-Boot somehow ? :)

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Mon, Apr 30, 2018 at 08:29:56PM +, Otavio Salvador wrote: > On Mon, Apr 30, 2018 at 5:25 PM Tom Rini wrote: > > > On Mon, Apr 30, 2018 at 07:57:18PM +, Otavio Salvador wrote: > > > On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin < > > >

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/30/2018 10:29 PM, Otavio Salvador wrote: > On Mon, Apr 30, 2018 at 5:25 PM Tom Rini wrote: > >> On Mon, Apr 30, 2018 at 07:57:18PM +, Otavio Salvador wrote: >>> On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin < >>> alexander.kana...@linux.intel.com> wrote: >>>

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Mon, Apr 30, 2018 at 5:25 PM Tom Rini wrote: > On Mon, Apr 30, 2018 at 07:57:18PM +, Otavio Salvador wrote: > > On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin < > > alexander.kana...@linux.intel.com> wrote: > > > > > On 04/30/2018 08:25 PM, Marek Vasut wrote: > > >

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Mon, Apr 30, 2018 at 07:57:18PM +, Otavio Salvador wrote: > On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin < > alexander.kana...@linux.intel.com> wrote: > > > On 04/30/2018 08:25 PM, Marek Vasut wrote: > > Isn't it possible to solve your issue in the OE side? > > > > >>> > >

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Mon, Apr 30, 2018 at 4:53 PM Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 04/30/2018 08:25 PM, Marek Vasut wrote: > Isn't it possible to solve your issue in the OE side? > > >>> > >>> Can we NOT compile DTC alongside U-Boot somehow ? :) > >>> That'd be the most

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/30/2018 08:25 PM, Marek Vasut wrote: Isn't it possible to solve your issue in the OE side? Can we NOT compile DTC alongside U-Boot somehow ? :) That'd be the most desired solution IMO. Yes please. Can you adjust the recipes and classes in oe-core, and remove the dtc recipe altogether?

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/30/2018 02:17 PM, Alexander Kanavin wrote: > On 04/16/2018 11:40 AM, Marek Vasut wrote: >>> Isn't it possible to solve your issue in the OE side? >>> >> >> Can we NOT compile DTC alongside U-Boot somehow ? :) >> That'd be the most desired solution IMO. > > Yes please. Can you adjust the

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/16/2018 11:40 AM, Marek Vasut wrote: Isn't it possible to solve your issue in the OE side? Can we NOT compile DTC alongside U-Boot somehow ? :) That'd be the most desired solution IMO. Yes please. Can you adjust the recipes and classes in oe-core, and remove the dtc recipe

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

Hi, Update: This rocko 2.4/u-boot combination still seems to work[1]: Note that this is before rocko 2.4.1 and before U-Boot 2018.01. => version U-Boot 2017.09 (Nov 04 2017 - 20:32:29 +) arm-poky-linux-gnueabi-gcc (GCC) 7.2.0 GNU ld (GNU Binutils) 2.29.0.20170912 [1]

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

Hi, Please see my comments below. On 2018-04-11 16:51, Marek Vasut wrote: On 04/11/2018 04:47 PM, Burton, Ross wrote: On 9 April 2018 at 00:02, Marek Vasut wrote: This upgrades the U-Boot from 2018.01 to 2018.03 release and drops patches accepted upstream, getting the patch

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

t; ma...@denx.de; raj.k...@gmail.com >> Cc: ota...@ossystems.com.br; openembedded-core@lists.openembedded.org >> Subject: Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release >> >> Hi, >> >> On 2018-04-11 04:28, yamada.masah...@socionext.com wrote: >>&g

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/11/2018 04:47 PM, Burton, Ross wrote: > On 9 April 2018 at 00:02, Marek Vasut wrote: >> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops >> patches accepted upstream, getting the patch count to zero. > > Are you proposing this for 2.5/Sumo (breaking the

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 9 April 2018 at 00:02, Marek Vasut wrote: > This upgrades the U-Boot from 2018.01 to 2018.03 release and drops > patches accepted upstream, getting the patch count to zero. Are you proposing this for 2.5/Sumo (breaking the freeze) or is it fine to sit in master-next until 2.5

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

<raj.k...@gmail.com> Cc: Otavio Salvador <ota...@ossystems.com.br>; openembedded-core@lists.openembedded.org; Yamada, Masahiro/山田 真弘 <yamada.masah...@socionext.com> Subject: Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release On 04/10/2018 11:49 AM, Martin Hundebøll wrote: Hi,

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

Hi, I had to patch up our own u-boot recipe as shown in the attached patch to make v2018.03 compile for qemu-x86. The thing is that the build of pylibfdt became unconditional since 15b97f5c5e ('pylibfdt: move pylibfdt to scripts/dtc/pylibfdt and refactor makefile') In my case

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/10/2018 11:49 AM, Martin Hundebøll wrote: > Hi, Hi, > I had to patch up our own u-boot recipe as shown in the attached patch > to make v2018.03 compile for qemu-x86. > > The thing is that the build of pylibfdt became unconditional since > 15b97f5c5e ('pylibfdt: move pylibfdt to

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/09/2018 03:48 PM, Khem Raj wrote: > On Mon, Apr 9, 2018 at 1:25 AM, Marek Vasut wrote: >> On 04/09/2018 02:54 AM, Khem Raj wrote: >>> >>> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut >> > wrote: >>> >>> This upgrades the U-Boot from

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Mon, Apr 9, 2018 at 1:25 AM, Marek Vasut wrote: > On 04/09/2018 02:54 AM, Khem Raj wrote: >> >> On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut > > wrote: >> >> This upgrades the U-Boot from 2018.01 to 2018.03 release and drops >> patches

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On 04/09/2018 02:54 AM, Khem Raj wrote: > > On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut > wrote: > > This upgrades the U-Boot from 2018.01 to 2018.03 release and drops > patches accepted upstream, getting the patch count to zero. > > > > It fails

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

Isn't it fail again because of autodetected swig from host? Since 2017.07 I have: do_compile_prepend () { sed 's@\(^always += $(if $(shell which swig 2> /dev/null),_libfdt.so)$\)@# do not autodetect swig, there is no swig-native dependency \1@g' -i ${S}/tools/Makefile } to prevent

Re: [OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

On Sun, Apr 8, 2018 at 4:10 PM Marek Vasut wrote: > This upgrades the U-Boot from 2018.01 to 2018.03 release and drops > patches accepted upstream, getting the patch count to zero. It fails for me if I have libfdt installed on build host It seems build is doing the include

[OE-core] [PATCH] u-boot: Upgrade to 2018.03 release

This upgrades the U-Boot from 2018.01 to 2018.03 release and drops patches accepted upstream, getting the patch count to zero. Signed-off-by: Marek Vasut Cc: Otavio Salvador Cc: Ross Burton Cc: Richard Purdie