u-boot: mainline
cover u-boot: mainline
This set of patches add a new u-boot-common file for 2017.05, so it can be shared between u-boot-rockchip and a u-boot recipe for mainline. Then, it add a bbappend to bump u-boot to the last v2017.05.
Romain Perier (3):
u-boot: Add u-boot-common_2017.05.inc
u-boot-rockchip: Use u-boot-common_2017.05.inc
u-boot: Add bbappend for u-boot mainline
recipes-bsp/u-boot/u-boot-common_2017.05.inc | 14 ++++++++++++++ recipes-bsp/u-boot/u-boot-rockchip_git.bb | 2 +- recipes-bsp/u-boot/u-boot_%.bbappend | 5 +++++ 3 files changed, 20 insertions(+), 1 deletion(-) create mode 100644 recipes-bsp/u-boot/u-boot-common_2017.05.inc create mode 100644 recipes-bsp/u-boot/u-boot_%.bbappend
Signature · 1 line
1.8.3.1
PATCH 1/3 u-boot: Add u-boot-common_2017.05.inc
This adds new common file for u-boot 2017.05, so u-boot mainline recipe and u-boot-rockchip can share common information about this version.
--- recipes-bsp/u-boot/u-boot-common_2017.05.inc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 recipes-bsp/u-boot/u-boot-common_2017.05.inc
recipes-bsp/u-boot/u-boot-common_2017.05.inc new file +14 -0
@@ -0,0 +1,14 @@ +HOMEPAGE = "http://www.denx.de/wiki/U-Boot/WebHome" +SECTION = "bootloaders" + +LICENSE = "GPLv2+" +LIC_FILES_CHKSUM = "file://Licenses/README;md5=a2c678cfd4a4d97135585cad908541c6" +PE = "1" + +# We use the revision in order to avoid having to fetch it from the +# repo during parse +SRCREV = "64c4ffa9fa223f7ae8640f9c8f3044bfa0e3bfda" + +SRC_URI = "git://git.denx.de/u-boot.git" + +S = "${WORKDIR}/git"
Signature · 1 line
1.8.3.1
PATCH 2/3 u-boot-rockchip: Use u-boot-common_2017.05.inc
In reply to Romain PerierNow, use the new common include file for u-boot
--- recipes-bsp/u-boot/u-boot-rockchip_git.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
recipes-bsp/u-boot/u-boot-rockchip_git.bb +1 -1
@@ -4,7 +4,7 @@ # Released under the MIT license (see COPYING.MIT for the terms) require recipes-bsp/u-boot/u-boot.inc -require recipes-bsp/u-boot/u-boot-common_2017.01.inc +require u-boot-common_2017.05.inc DESCRIPTION = "Rockchip next-dev U-Boot" COMPATIBLE_MACHINE = "(firefly-rk3288|rock2-square)"
Signature · 1 line
1.8.3.1
PATCH 3/3 u-boot: Add bbappend for u-boot mainline
In reply to Romain PerierThis bumps u-boot mainline to the last v2017.05
--- recipes-bsp/u-boot/u-boot_%.bbappend | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 recipes-bsp/u-boot/u-boot_%.bbappend
recipes-bsp/u-boot/u-boot_%.bbappend new file +5 -0
@@ -0,0 +1,5 @@ +PV="2017.05" + +require u-boot-common_${PV}.inc + +DEPENDS += "bc-native dtc-native"
Signature · 1 line
1.8.3.1
u-boot 2017.05 was released May 10. Wouldn't it be better to update oe-core's u-boot to 2017.05 then just add any differences in meta-rockchip?
Quoted 20 lines · Romain Perier
This set of patches add a new u-boot-common file for 2017.05, so it can be shared between u-boot-rockchip and a u-boot recipe for mainline. Then, it add a bbappend to bump u-boot to the last v2017.05.
Romain Perier (3):
u-boot: Add u-boot-common_2017.05.inc
u-boot-rockchip: Use u-boot-common_2017.05.inc
u-boot: Add bbappend for u-boot mainlinerecipes-bsp/u-boot/u-boot-common_2017.05.inc | 14 ++++++++++++++ recipes-bsp/u-boot/u-boot-rockchip_git.bb | 2 +- recipes-bsp/u-boot/u-boot_%.bbappend | 5 +++++ 3 files changed, 20 insertions(+), 1 deletion(-) create mode 100644 recipes-bsp/u-boot/u-boot-common_2017.05.inc create mode 100644 recipes-bsp/u-boot/u-boot_%.bbappend--
1.8.3.1
Hello,
Quoted 3 lines · Trevor Woerner
u-boot 2017.05 was released May 10. Wouldn't it be better to update oe-core's u-boot to 2017.05 then just add any differences in meta-rockchip?
Good idea yes. I will bump u-boot-common_${PV} and u-boot_2017.01 to v2017.05 in poky (and then propose changes in meta-rockchip) Regards,
Romain
Quoted 23 lines
Quoted 20 lines · Romain Perier
This set of patches add a new u-boot-common file for 2017.05, so it can be shared between u-boot-rockchip and a u-boot recipe for mainline. Then, it add a bbappend to bump u-boot to the last v2017.05.
Romain Perier (3):
u-boot: Add u-boot-common_2017.05.inc
u-boot-rockchip: Use u-boot-common_2017.05.inc
u-boot: Add bbappend for u-boot mainlinerecipes-bsp/u-boot/u-boot-common_2017.05.inc | 14 ++++++++++++++ recipes-bsp/u-boot/u-boot-rockchip_git.bb | 2 +- recipes-bsp/u-boot/u-boot_%.bbappend | 5 +++++ 3 files changed, 20 insertions(+), 1 deletion(-) create mode 100644 recipes-bsp/u-boot/u-boot-common_2017.05.inc create mode 100644 recipes-bsp/u-boot/u-boot_%.bbappend--
1.8.3.1
Quoted 7 lines · Romain Perier
Quoted 3 lines · Trevor Woerner
u-boot 2017.05 was released May 10. Wouldn't it be better to update oe-core's u-boot to 2017.05 then just add any differences in meta-rockchip?
Good idea yes. I will bump u-boot-common_${PV} and u-boot_2017.01 to v2017.05 in poky (and then propose changes in meta-rockchip)
Changes to u-boot should be sent to openembedded-core; poky gets updated from there (not vice versa).
Hello,
Quoted 10 lines · Trevor Woerner
Quoted 6 lines · Romain Perier
Quoted 3 lines · Trevor Woerner
u-boot 2017.05 was released May 10. Wouldn't it be better to update oe-core's u-boot to 2017.05 then just add any differences in meta-rockchip?
Good idea yes. I will bump u-boot-common_${PV} and u-boot_2017.01 to v2017.05 in poky (and then propose changes in meta-rockchip)
Changes to u-boot should be sent to openembedded-core; poky gets updated from there (not vice versa).
Even, if I Cc: the ML oe-core and yocto ? (so I have to do the changes in oe-core directly, I mean the repo. right ?)
Regards,
Romain
Hi Romain,
Quoted 7 lines · Romain Perier
Quoted 6 lines · Trevor Woerner
Quoted 4 lines · Romain Perier
Quoted 3 lines · Trevor Woerner
u-boot 2017.05 was released May 10. Wouldn't it be better to update oe-core's u-boot to 2017.05 then just add any differences in meta-rockchip?
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Good idea yes. I will bump u-boot-common_${PV} and u-boot_2017.01 to v2017.05 in poky (and then propose changes in meta-rockchip)
Changes to u-boot should be sent to openembedded-core; poky gets updated from there (not vice versa).
Even, if I Cc: the ML oe-core and yocto ? (so I have to do the changes in oe-core directly, I mean the repo. right ?)
Yes. The "home" of the u-boot recipe is in openembedded-core. Please send any updates/changes to the u-boot recipe to the openembedded-core mailing list [http://lists.openembedded.org/mailman/listinfo/openembedded-core].
CC'ing it to other lists would not be polite since most OE/Yocto lists receive quite a lot of traffic already and this would be a non-relevant email to them.
Poky is derived from a bunch of sources, primarily openembedded-core, plus some small additions of its own. Only when you want to change one of these small additions would you send a patch to the poky mailing list directly (which isn't the case with u-boot).
Quoted 10 lines · Romain Perier
Hello,
Quoted 6 lines · Trevor Woerner
Quoted 4 lines · Romain Perier
Quoted 3 lines · Trevor Woerner
u-boot 2017.05 was released May 10. Wouldn't it be better to update oe-core's u-boot to 2017.05 then just add any differences in meta-rockchip?
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Good idea yes. I will bump u-boot-common_${PV} and u-boot_2017.01 to v2017.05 in poky (and then propose changes in meta-rockchip)
Changes to u-boot should be sent to openembedded-core; poky gets updated from there (not vice versa).
Even, if I Cc: the ML oe-core and yocto ? (so I have to do the changes in oe-core directly, I mean the repo. right ?)
I'd check with Marex the u-boot maintainer also. He may have something queued up. It is entirely possible he isn't on this list.
Also, one factor will be timing of u-boot releases versus the next YP release. That will determine final version.
Philip
Quoted 4 lines
Regards,
Romain
Quoted 2 lines · Philip Balister
I'd check with Marex the u-boot maintainer also. He may have something queued up. It is entirely possible he isn't on this list.
Good point. Marek just posted a 2017.05 update to oecore :-)