Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 09/23/2017 01:36 AM, Martin Jansa wrote: > On Sat, Sep 23, 2017 at 12:19:27AM +0200, Marek Vasut wrote: >> Agreed. So what is the conclusion here about this , are we updating to >> 2017.09 or not ? > > It was already merged couple days ago: >

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On Sat, Sep 23, 2017 at 12:19:27AM +0200, Marek Vasut wrote: > Agreed. So what is the conclusion here about this , are we updating to > 2017.09 or not ? It was already merged couple days ago: http://git.openembedded.org/openembedded-core/commit/?id=340d413f678a4a64dfa060e8fe0ac721b73fed97 and

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

Hi Marek, On Fri, Sep 22, 2017 at 3:19 PM, Marek Vasut wrote: > On 09/21/2017 11:35 PM, Philip Balister wrote: >> On 09/19/2017 04:15 AM, Marek Vasut wrote: >>> On 09/18/2017 06:06 PM, Tom Rini wrote: On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote: > On 18

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 09/21/2017 11:35 PM, Philip Balister wrote: > On 09/19/2017 04:15 AM, Marek Vasut wrote: >> On 09/18/2017 06:06 PM, Tom Rini wrote: >>> On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote: On 18 September 2017 at 16:46, Otavio Salvador < otavio.salva...@ossystems.com.br>

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 09/18/2017 06:06 PM, Tom Rini wrote: > On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote: >> On 18 September 2017 at 16:46, Otavio Salvador < >> otavio.salva...@ossystems.com.br> wrote: >> >>> What is the policy on doing u-boot version upgrades this late in the >>> >>> release cycle?

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 2017-09-17 11:35 AM, Khem Raj wrote: I am seeing same failures too. havent yet dug into it. Same here. Jackie said that he's going to investigate now. We've only seen this failure since 2017-09-15 06:00 AM ET after we rebased onto 2017-09-14 content/ this commit: 583dca2

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 18 September 2017 at 16:46, Otavio Salvador < otavio.salva...@ossystems.com.br> wrote: > What is the policy on doing u-boot version upgrades this late in the > > release cycle? SHouldn't this wait until after the release? > > > Why? > > It is just another recipe and we are upgrading to the

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote: > On 18 September 2017 at 16:46, Otavio Salvador < > otavio.salva...@ossystems.com.br> wrote: > > > What is the policy on doing u-boot version upgrades this late in the > > > > release cycle? SHouldn't this wait until after the

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

Em 18 de set de 2017 12:20 PM, "Philip Balister" escreveu: On 09/18/2017 02:39 AM, Martin Jansa wrote: > On Mon, Sep 18, 2017 at 10:31:05AM +0200, Marek Vasut wrote: >> On 09/18/2017 09:54 AM, Martin Jansa wrote: >>> u-boot-fw-utils-cross is broken for at least a year, if it

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 09/18/2017 02:39 AM, Martin Jansa wrote: > On Mon, Sep 18, 2017 at 10:31:05AM +0200, Marek Vasut wrote: >> On 09/18/2017 09:54 AM, Martin Jansa wrote: >>> u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot >>> of boards, why nobody complained yet? >> >> Didn't you say it

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On Mon, Sep 18, 2017 at 10:31:05AM +0200, Marek Vasut wrote: > On 09/18/2017 09:54 AM, Martin Jansa wrote: > > u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot > > of boards, why nobody complained yet? > > Didn't you say it worked for 2017.07 or did I misunderstand that ?

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot of boards, why nobody complained yet? On Mon, Sep 18, 2017 at 7:32 AM, Marek Vasut wrote: > On 09/17/2017 01:06 PM, Martin Jansa wrote: > > I've verified that u-boot-fw-utils builds and installs

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

Hi Khem, On Sun, Sep 17, 2017 at 2:18 AM, Martin Jansa wrote: Is anyone seeing u-boot-fw-utils.do_install failure with this? I am seeing same failures too. havent yet dug into it. Please pay note to change in directory structure in u-boot envs (from 2017.09):

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On 09/18/2017 09:54 AM, Martin Jansa wrote: > u-boot-fw-utils-cross is broken for at least a year, if it breaks a lot > of boards, why nobody complained yet? Didn't you say it worked for 2017.07 or did I misunderstand that ? btw stop top-posting please. > On Mon, Sep 18, 2017 at 7:32 AM, Marek

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

On Sun, Sep 17, 2017 at 2:18 AM, Martin Jansa wrote: > Is anyone seeing u-boot-fw-utils.do_install failure with this? > I am seeing same failures too. havent yet dug into it. > u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or > directory > > I've

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

Is anyone seeing u-boot-fw-utils.do_install failure with this? u-boot-fw-utils/1_2017.09-r0/git/tools/env/fw_printenv: No such file or directory I've tried u-boot-fw-utils-cross, but it fails as well even sooner in do_compile: Log data follows: | DEBUG: Executing shell function do_compile |

Re: [U-Boot] [OE-core] [PATCH] u-boot: Upgrade to 2017.09

I've verified that u-boot-fw-utils builds and installs fw_printenv correctly with 2017.07. And that u-boot-fw-utils-cross was broken even with Yocto 2.3 Pyro and 2017.01 version there, maybe it's time to remove cross version? As nobody is using it and it's not tested? On Sun, Sep 17, 2017 at