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

[Marek Vasut]

On 11/17/2017 09:59 PM, Tom Rini wrote:
> On Fri, Nov 17, 2017 at 08:19:07PM +0100, Marek Vasut wrote:
>> On 11/14/2017 07:32 PM, Otavio Salvador wrote:
>>> This upgrades the U-Boot from 2017.09 to 2017.11 release.
>>>
>>> Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
>>> ---
>>>
>>>  .../u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc}     | 2 +-
>>>  .../u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb}   | 0
>>>  .../u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb}     | 0
>>>  meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb}        | 0
>>>  4 files changed, 1 insertion(+), 1 deletion(-)
>>>  rename meta/recipes-bsp/u-boot/{u-boot-common_2017.09.inc => u-boot-common_2017.11.inc} (89%)
>>>  rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.09.bb => u-boot-fw-utils_2017.11.bb} (100%)
>>>  rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.09.bb => u-boot-mkimage_2017.11.bb} (100%)
>>>  rename meta/recipes-bsp/u-boot/{u-boot_2017.09.bb => u-boot_2017.11.bb} (100%)
>>>
>>> diff --git a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>> similarity index 89%
>>> rename from meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
>>> rename to meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>> index 02e51242cb..bfdf1a0d8f 100644
>>> --- a/meta/recipes-bsp/u-boot/u-boot-common_2017.09.inc
>>> +++ b/meta/recipes-bsp/u-boot/u-boot-common_2017.11.inc
>>> @@ -7,7 +7,7 @@ PE = "1"
>>>  
>>>  # We use the revision in order to avoid having to fetch it from the
>>>  # repo during parse
>>> -SRCREV = "c98ac3487e413c71e5d36322ef3324b21c6f60f9"
>>> +SRCREV = "c253573f3e269fd9a24ee6684d87dd91106018a5"
>>>  
>>>  SRC_URI = "git://git.denx.de/u-boot.git \
>>>      file://MPC8315ERDB-enable-DHCP.patch \
>>
>> This patch ^ could use a refresh , since it applies with Fuzz now.
> 
> Honestly, just enable DISTRO_DEFAULTS for the board and post that
> upstream instead.

Or that, but someone would have to test that first and the patch author
does not respond for some reason.

-- 
Best regards,
Marek Vasut