u-boot: Update to 2017.03 release
PATCH 1/1 u-boot: Update to 2017.03 release
Upgrade U-Boot to the latest version.
---
.../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 +-
.../u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb} | 0
.../u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} | 0
meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} | 0
4 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-bsp/u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} (86%)
rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb} (100%)
rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} (100%)
rename meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} (100%)meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc renamed from meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc +1 -1
@@ -7,7 +7,7 @@ PE = "1" # We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149" +SRCREV = "8537ddd769f460d7fb7a62a3dcc9669049702e51" SRC_URI = "git://git.denx.de/u-boot.git"
meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb renamed from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb +0 -0
meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb renamed from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb +0 -0
meta/recipes-bsp/u-boot/u-boot_2017.03.bb renamed from meta/recipes-bsp/u-boot/u-boot_2017.01.bb +0 -0
Signature · 1 line
2.11.0
Some background is needed ....
Marex sent in the 2017.01 update after discussions in irc about timing of u-boot releases and the YP release schedule. The 2017.03 release would happen after oe-core passed the feature freeze. So, at the time people felt the release should have 2017.01.
People consuming the u-boot recipe via a bbappends have been using 2017.01 for their bsp's. Changing at this time is potentially a pain point, and has some technical risk on the release schedule.
On the other hand, people working to get their code upstream, might be frustrated having to wait until fall to use a current u-boot release.
Should we go ahead and add the 2017.03 recipe and use DEFAULT_PREFERENCE to turn it off?
Also, this would be a good time to determine who the maintainers of the recipes are.
Philip
Quoted 46 lines · Marek Vasut
Upgrade U-Boot to the latest version.
Signed-off-by Marek Vasut <[email protected]>Cc Denys Dmytriyenko <[email protected]>Cc Richard Purdie <[email protected]>Cc Ross Burton <[email protected]>--- .../u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} | 2 +- .../u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb} | 0 .../u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} | 0 meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} | 0 4 files changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{u-boot-common_2017.01.inc => u-boot-common_2017.03.inc} (86%) rename meta/recipes-bsp/u-boot/{u-boot-fw-utils_2017.01.bb => u-boot-fw-utils_2017.03.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot-mkimage_2017.01.bb => u-boot-mkimage_2017.03.bb} (100%) rename meta/recipes-bsp/u-boot/{u-boot_2017.01.bb => u-boot_2017.03.bb} (100%)meta/recipes-bsp/u-boot/u-boot-common_2017.03.inc renamed from meta/recipes-bsp/u-boot/u-boot-common_2017.01.inc +1
-1@@ -7,7 +7,7 @@ PE = "1" # We use the revision in order to avoid having to fetch it from the # repo during parse -SRCREV = "a705ebc81b7f91bbd0ef7c634284208342901149" +SRCREV = "8537ddd769f460d7fb7a62a3dcc9669049702e51" SRC_URI = "git://git.denx.de/u-boot.git"meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.03.bb renamed from meta/recipes-bsp/u-boot/u-boot-fw-utils_2017.01.bb +0
-0meta/recipes-bsp/u-boot/u-boot-mkimage_2017.03.bb renamed from meta/recipes-bsp/u-boot/u-boot-mkimage_2017.01.bb +0
-0meta/recipes-bsp/u-boot/u-boot_2017.03.bb renamed from meta/recipes-bsp/u-boot/u-boot_2017.01.bb +0
-0