Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Berger <oecore.mailinglist@gmail.com>
To: Marek Vasut <marex@denx.de>, "Burton, Ross" <ross.burton@intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot: Upgrade to 2018.03 release
Date: Sat, 21 Apr 2018 12:01:53 +0200	[thread overview]
Message-ID: <9c70891a-afc7-9f55-e231-bc1c3eb4dce3@gmail.com> (raw)
In-Reply-To: <2c318d94-b321-e83a-a5ef-254647b3d35e@denx.de>

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 <marex@denx.de> 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 is released?
> master-next, for 2.6 .
>
I think we have also problem with u-boot and rocko 2.4.x

I observed with 2.4.x for i.mx6 and sitara that u-boot 2017.01 does not 
function anymore properly (networking is broken due to compiler upgrade 
with 2.4.x [1]).

So I built u-boot 2017.03 (a pre-release version) with 2.4.1 and 2.4.2 
and it was fixed.

Please note, that I did not do this via bitbake, but using the SDK.

So I think it would be a good idea to get u-boot 2017.03 to build with a 
recent version of rocko as well.

[1] https://www.mail-archive.com/yocto@yoctoproject.org/msg39605.html

Regards,

Robert



  reply	other threads:[~2018-04-21 10:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-08 23:02 [PATCH] u-boot: Upgrade to 2018.03 release Marek Vasut
2018-04-09  0:54 ` Khem Raj
2018-04-09  7:12   ` Martin Jansa
2018-04-09  8:25   ` Marek Vasut
2018-04-09 13:48     ` Khem Raj
2018-04-09 15:24       ` Marek Vasut
2018-04-10  9:49   ` Martin Hundebøll
2018-04-10  9:55     ` Marek Vasut
     [not found]       ` <d89b39f665a14c63b0821c1ad600da72@SOC-EX01V.e01.socionext.com>
2018-04-11  8:42         ` Martin Hundebøll
     [not found]           ` <32a348ed6176434db8178d29d7e1f183@SOC-EX01V.e01.socionext.com>
2018-04-16  8:40             ` Marek Vasut
2018-04-30 12:17               ` Alexander Kanavin
2018-04-30 17:25                 ` Marek Vasut
2018-04-30 18:05                   ` Martin Hundebøll
2018-04-30 19:46                   ` Alexander Kanavin
2018-04-30 19:57                     ` Otavio Salvador
2018-04-30 20:25                       ` Tom Rini
2018-04-30 20:29                         ` Otavio Salvador
2018-04-30 23:30                           ` Marek Vasut
2018-05-01  0:25                           ` Tom Rini
2018-05-01  1:56                             ` Otavio Salvador
2018-04-11 14:47 ` Burton, Ross
2018-04-11 14:51   ` Marek Vasut
2018-04-21 10:01     ` Robert Berger [this message]
2018-04-21 10:52     ` Robert Berger

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=9c70891a-afc7-9f55-e231-bc1c3eb4dce3@gmail.com \
    --to=oecore.mailinglist@gmail.com \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=ross.burton@intel.com \
    /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