recipes-bsp: u-boot-ti-mainline: Update to v2021.04 release

Update u-boot recipe to be on the bleeding upstream tag.

While at it, also update the u-boot source url to point to the new
server as per [1].

While it may be redundant, lets document the usage of URI and
PROTOCOL for those, who (cough), may get tripped otherwise.

[1] https://source.denx.de/u-boot/u-boot/-/commit/a3bbd0b912f9afff745247fe9641961875322926

Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>

1 files changed, 12 insertions, 4 deletions

diff --git a/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb b/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb
index ee0b1764..0d3f33ef 100644
--- a/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-mainline_git.bb
@@ -4,7 +4,15 @@ LIC_FILES_CHKSUM = "file://Licenses/README;md5=5a7450c57ffe5ae63fd732446b988025"
 
 PR = "r0"
 
-PV = "2020.10"
-UBOOT_GIT_URI = "git://gitlab.denx.de/u-boot/u-boot.git"
-UBOOT_GIT_PROTOCOL = "http"
-SRCREV = "050acee119b3757fee3bd128f55d720fdd9bb890"
+PV = "2021.04"
+
+# For the un-initiated:
+# The actual URL you'd use with a git clone for example would be:
+# https://source.denx.de/u-boot/u-boot.git/
+# However, in the context of OE, we have to explicitly split things up:
+# a) we want it to use git fetcher - hence git:// prefix in GIT_URI (if we
+#  used https here, we'd endup attempting wget instead of git)
+# b) and we want git fetcher to use https protocol, hence GIT_PROTOCOL as https
+UBOOT_GIT_URI = "git://source.denx.de/u-boot/u-boot.git"
+UBOOT_GIT_PROTOCOL = "https"
+SRCREV = "b46dd116ce03e235f2a7d4843c6278e1da44b5e1"