From: Vagrant Cascadian <vagrant@debian.org>
To: 31426@debbugs.gnu.org
Subject: [bug#31426] Update u-boot to 2018.05
Date: Fri, 11 May 2018 16:37:52 -0700 [thread overview]
Message-ID: <87tvrdvk4v.fsf@aikidev.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 147 bytes --]
The attached patch updates u-boot to 2018.05.
It has been build-tested all u-boot-* targets, and boot tested on
wandboard.
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-gnu-u-boot-Update-to-2018.05.patch --]
[-- Type: text/x-diff, Size: 1321 bytes --]
From 51fcdd3f3d8461e43764ec73dd50cd4414713095 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Fri, 11 May 2018 22:59:44 +0000
Subject: [PATCH] gnu: u-boot: Update to 2018.05.
* gnu/packages/bootloaders.scm (u-boot): Update to 2018.05.
---
gnu/packages/bootloaders.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
index c0a0101c5..b72858f7b 100644
--- a/gnu/packages/bootloaders.scm
+++ b/gnu/packages/bootloaders.scm
@@ -338,7 +338,7 @@ tree binary files. These are board description files used by Linux and BSD.")
(define u-boot
(package
(name "u-boot")
- (version "2018.01")
+ (version "2018.05")
(source (origin
(method url-fetch)
(uri (string-append
@@ -346,7 +346,7 @@ tree binary files. These are board description files used by Linux and BSD.")
"u-boot-" version ".tar.bz2"))
(sha256
(base32
- "1nidnnjprgxdhiiz7gmaj8cgcf52l5gbv64cmzjq4gmkjirmk3wk"))))
+ "0j60p4iskzb4hamxgykc6gd7xchxfka1zwh8hv08r9rrc4m3r8ad"))))
(native-inputs
`(("bc" ,bc)
;("dtc" ,dtc) ; they have their own incompatible copy.
--
2.17.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2018-05-11 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 23:37 Vagrant Cascadian [this message]
2018-05-12 8:39 ` bug#31426: Update u-boot to 2018.05 Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvrdvk4v.fsf@aikidev.net \
--to=vagrant@debian.org \
--cc=31426@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.