From: Herman Rimm via Guix-patches via <guix-patches@gnu.org>
To: 72987@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>,
Vagrant Cascadian <vagrant@debian.org>
Subject: [bug#72987] [PATCH v3 0/5] Add U-Boot patches and bootloaders.
Date: Fri, 13 Dec 2024 22:07:31 +0100 [thread overview]
Message-ID: <cover.1734122005.git.herman@rimm.ee> (raw)
In-Reply-To: <20240902190459.13783-1-herman@rimm.ee>
Hello,
This revision depends on #74842 and #74849, in addition to #70131.
The top-level U-Boot patches are removed in #70131 instead of in the
first patch, and the Nano Pi R4S and Orange Pi Zero 2W bootloaders are
added in the second and fourth instead of in #70131.
The final patch adds a bootloader for the ASUS Tinker Board S and the
ARM Trusted Firmware for its SoC. The HDMI is flaky.
I could create an additional U-Boot package for the Nano Pi R4S, and
apply the DDR3 patch to it instead, so both variants are supported.
Cheers,
Herman
Herman Rimm (5):
gnu: u-boot: Enlarge space available for kernel.
gnu: bootloader: Add nanopi-r4s-rk3399 bootloader.
gnu: u-boot: Use DDR3 patch for Nano Pi R4S.
gnu: bootloader: Add orangepi-zero2w bootloader.
gnu: bootloader: Add ASUS Tinker Board S bootloader.
gnu/bootloader/u-boot.scm | 22 ++++++++
gnu/local.mk | 4 +-
gnu/packages/bootloaders.scm | 43 ++++++++++++++-
gnu/packages/firmware.scm | 9 +++
gnu/packages/patches/u-boot-50M-kernel.patch | 55 +++++++++++++++++++
.../patches/u-boot-nanopi-r4s-ddr3.patch | 33 +++++++++++
6 files changed, 164 insertions(+), 2 deletions(-)
create mode 100644 gnu/packages/patches/u-boot-50M-kernel.patch
create mode 100644 gnu/packages/patches/u-boot-nanopi-r4s-ddr3.patch
base-commit: 383e7ca281bae36a151f3fdb2e3a1ac4c5c65b50
--
2.45.2
next prev parent reply other threads:[~2024-12-13 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 19:04 [bug#72987] [PATCH] gnu: u-boot: Enlarge space available for kernel Herman Rimm via Guix-patches via
2024-09-15 22:12 ` Ludovic Courtès
2024-09-16 17:24 ` [bug#72987] [PATCH v2] " Herman Rimm via Guix-patches via
2024-09-16 21:05 ` [bug#72987] u-boot: rpi: " Vagrant Cascadian
2024-09-19 14:11 ` Simon Glass
2024-09-16 21:10 ` [bug#72987] [PATCH v2] gnu: u-boot: " Vagrant Cascadian
2024-09-19 10:50 ` [bug#70131] " Herman Rimm via Guix-patches via
2024-09-20 21:52 ` Vagrant Cascadian
2024-12-13 21:07 ` Herman Rimm via Guix-patches via [this message]
2024-12-13 21:07 ` [bug#72987] [PATCH v3 1/5] " Herman Rimm via Guix-patches via
2024-12-13 21:07 ` [bug#72987] [PATCH v3 2/5] gnu: bootloader: Add nanopi-r4s-rk3399 bootloader Herman Rimm via Guix-patches via
2024-12-13 21:07 ` [bug#72987] [PATCH v3 3/5] gnu: u-boot: Use DDR3 patch for Nano Pi R4S Herman Rimm via Guix-patches via
2024-12-13 21:07 ` [bug#72987] [PATCH v3 4/5] gnu: bootloader: Add orangepi-zero2w bootloader Herman Rimm via Guix-patches via
2024-12-13 21:07 ` [bug#72987] [PATCH v3 5/5] gnu: bootloader: Add ASUS Tinker Board S bootloader Herman Rimm via Guix-patches via
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=cover.1734122005.git.herman@rimm.ee \
--to=guix-patches@gnu.org \
--cc=72987@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=herman@rimm.ee \
--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 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.