From: nomble@palism.com
To: 37741@debbugs.gnu.org
Cc: Vagrant Cascadian <vagrant@debian.org>,
Danny Milosavljevic <dannym@scratchpost.org>,
Caliph Nomble <nomble@palism.com>
Subject: [bug#37741] [PATCH 0/3] Update u-boot to 2019.10 and add u-boot-rockpro64-rk3399.
Date: Sun, 13 Oct 2019 20:14:07 -0400 [thread overview]
Message-ID: <20191014001407.28367-1-nomble@palism.com> (raw)
From: Caliph Nomble <nomble@palism.com>
Blobless LPDDR4 training for the rk3399 was just added in u-boot 2019.10,
necessitating the update. Patches combined into a single set for that reason.
U-boot patch removed due to mainlining.
Caliph Nomble (3):
gnu: u-boot: Update to 2019.10.
gnu: Add arm-trusted-firmware-rk3399.
gnu: Add u-boot-rockpro64-rk3399
gnu/bootloader/u-boot.scm | 17 ++++++
gnu/local.mk | 1 -
gnu/packages/bootloaders.scm | 27 +++++++--
gnu/packages/firmware.scm | 23 ++++++++
...boot-fix-mkimage-header-verification.patch | 57 -------------------
gnu/system/install.scm | 6 ++
6 files changed, 68 insertions(+), 63 deletions(-)
delete mode 100644 gnu/packages/patches/u-boot-fix-mkimage-header-verification.patch
--
2.21.0
next reply other threads:[~2019-10-14 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 0:14 nomble [this message]
2019-10-14 6:01 ` [bug#37741] [PATCH 1/3] gnu: u-boot: Update to 2019.10 nomble
2019-10-15 4:07 ` Vagrant Cascadian
2019-10-14 6:01 ` [bug#37741] [PATCH 2/3] gnu: Add arm-trusted-firmware-rk3399 nomble
2019-10-15 4:02 ` Vagrant Cascadian
2019-10-15 6:38 ` Kever Yang
2019-10-17 5:46 ` Vagrant Cascadian
2019-10-17 6:43 ` Kever Yang
2019-10-18 19:22 ` Vagrant Cascadian
2019-10-14 6:01 ` [bug#37741] [PATCH 3/3] gnu: Add u-boot-rockpro64-rk3399 nomble
2019-10-18 20:44 ` bug#37741: [PATCH 0/3] Update u-boot to 2019.10 and add u-boot-rockpro64-rk3399 Vagrant Cascadian
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191014001407.28367-1-nomble@palism.com \
--to=nomble@palism.com \
--cc=37741@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=vagrant@debian.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).