u-boot-rockchip: update require path
PATCH 1/1 u-boot-rockchip: update require path
The oe-core recipe was updated (2017.05 -> 2017.07), this recipe needed to be updated to suit. However, this u-boot (from rockchip) is still at version 2017.05.
--- 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.05.inc +require recipes-bsp/u-boot/u-boot-common_2017.07.inc DESCRIPTION = "Rockchip next-dev U-Boot" COMPATIBLE_MACHINE = "(firefly-rk3288|rock2-square)"
Signature · 1 line
2.13.0
Quoted 5 lines · Trevor Woerner
The oe-core recipe was updated (2017.05 -> 2017.07), this recipe needed to be updated to suit. However, this u-boot (from rockchip) is still at version 2017.05.
Signed-off-by Trevor Woerner <[email protected]>
Not an objection, but, what's missing to move to just using upstream u-boot?
Signature · 1 line
Tom
Hey Tom,
Quoted 10 lines · Tom Rini
Quoted 5 lines · Trevor Woerner
The oe-core recipe was updated (2017.05 -> 2017.07), this recipe needed to be updated to suit. However, this u-boot (from rockchip) is still at version 2017.05.
Signed-off-by Trevor Woerner <[email protected]>Not an objection, but, what's missing to move to just using upstream u-boot?
Excellent question! I was just thinking the same thing myself as I was preparing this patch :-)
This patch is a maintenance patch that will allow builds to succeed, but I admit it isn't ideal.
At this point I'm hoping
http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139974.html
goes in so I can make 2 sets of recipes: one for rockchip components and one for upstream. At that point I'll evaluate all the upstream things and all the rockchip things to make sure they work on the boards I have. At that point I can clean all this up.
Hopefully I'll also be able to add the tinker board rk3288 and the firefly 3399.
Quoted 18 lines · Trevor Woerner
Hey Tom,
Quoted 9 lines · Tom Rini
Quoted 5 lines · Trevor Woerner
The oe-core recipe was updated (2017.05 -> 2017.07), this recipe needed to be updated to suit. However, this u-boot (from rockchip) is still at version 2017.05.
Signed-off-by Trevor Woerner <[email protected]>Not an objection, but, what's missing to move to just using upstream u-boot?
Excellent question! I was just thinking the same thing myself as I was preparing this patch :-)
This patch is a maintenance patch that will allow builds to succeed, but I admit it isn't ideal.
Quoted 8 lines
At this point I'm hoping
http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139974.html
goes in so I can make 2 sets of recipes: one for rockchip components and one for upstream. At that point I'll evaluate all the upstream things and all the rockchip things to make sure they work on the boards I have. At that point I can clean all this up.Hopefully I'll also be able to add the tinker board rk3288 and the firefly 3399.
I have a small layer I use for booting mainline components on the tinker, so i can confirm that works with current upstream.
Quoted 4 lines · Jack Mitchell
I have a small layer I use for booting mainline components on the tinker, so i can confirm that works with current upstream.
Thanks! :-D