[OE-core] [PATCH] u-boot: Update to 2017.03 release

[Philip Balister]

On 03/30/2017 02:06 PM, Denys Dmytriyenko wrote:
> On Thu, Mar 30, 2017 at 04:12:08PM +0200, Marek Vasut wrote:
>> On 03/30/2017 03:24 PM, Denys Dmytriyenko wrote:
>>> On Thu, Mar 30, 2017 at 10:21:31AM +0200, Marek Vasut wrote:
>>>> On 03/29/2017 11:56 PM, Denys Dmytriyenko wrote:
>>>>> On Mon, Mar 27, 2017 at 04:31:16PM +0200, Marek Vasut wrote:
>>>>>> On 03/27/2017 04:25 PM, Richard Purdie wrote:
>>>>>>> On Mon, 2017-03-27 at 16:22 +0200, Marek Vasut wrote:
>>>>>>>> Upgrade U-Boot to the latest version.
>>>>>>>
>>>>>>> Wrong list and how does this compare to Ovatio's patch?
>>>>>>
>>>>>> I was not CCed on Otavio's patch :(
>>>>>
>>>>> Yeah, me neither, unfortunately - people just ignore maintainers file now.
>>>>>
>>>>> Good thing Ross copied me on the other discussion!
>>>>>
>>>> Which other discussion ? :-(
>>>
>>> http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134682.html
>>>
>> I see. I'm all for updating to 2017.03 , since it fixes the OMAP serial
>> bug too :)
> 
> "Known devil is better than unknown angel"? :)
> 

I've got a machine under development that boots from the 2013.01 recipe
and a bbappend. I don't think it is a problem moving to .03, but I don't
know. I'm not sure how many other BSP's have done the same.

Meanwhile, I understand the desire of others who have work upstreamed in
u-boot they like to use with the next release.

How many u-boot releases are there a year? How do they line up with YP
releases? Should we carry two u-boot versions, similar to what happens
with the kernel?

Philip