From: Vagrant Cascadian <vagrant@debian.org>
To: 67261-done@debbugs.gnu.org
Cc: Herman Rimm <herman@rimm.ee>, Efraim Flashner <efraim@flashner.co.il>
Subject: bug#67261: [PATCH 0/3] Update u-boot to 2023.10.
Date: Fri, 22 Dec 2023 16:19:28 -0800 [thread overview]
Message-ID: <875y0p7otr.fsf@wireframe> (raw)
In-Reply-To: <cover.1700321434.git.herman@rimm.ee>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On 2023-11-18, Herman Rimm wrote:
> I use an OrangePi R1 Plus LTS with a u-boot v2023.10 bootloader. I have
> not performed any other tests. [PATCH 2/3], [PATCH 3/3] and boot log
> below for context.
Sorry it took so long to get around to this! ... Just in time for
2024.01 to roll around the corner in a couple weeks!
I have pushed to master as:
fad93748cd2d44f7f68d2d973a22ed0b438e657b gnu: u-boot: Update to 2023.10.
88fb95903c1d94b3be7e8a811d943af988041e4e gnu: bootloader: Add orangepi-r1-plus-lts-rk3328 bootloader.
ab1ff7ca40b0a2d935f715dcf64f0f3128632d3d images: Add orangepi-r1-plus-lts image.
I still wonder what to do long-term about which images should get built
out of the box, but for now the pattern seems to be add them if someone
wants them. Debian solved the issue of arbitrary number of images by
building the image in two parts, and concatenating the images
together. It is a bit rougher on the end-user to concatenate two images
together, but means the images can for the most part be shared across
all supported (and even unsupported) platforms, only the bootloader
areas differ:
https://deb.debian.org/debian/dists/bookworm/main/installer-arm64/20230607/images/netboot/SD-card-images/README.concatenateable_images
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2023-12-23 0:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 15:38 [bug#67261] [PATCH 0/3] Update u-boot to 2023.10 Herman Rimm via Guix-patches via
2023-11-18 16:01 ` [bug#67261] [PATCH 1/3] gnu: u-boot: Update " Herman Rimm via Guix-patches via
2023-11-24 21:23 ` Vagrant Cascadian
2023-11-18 16:01 ` [bug#67261] [PATCH 2/3] gnu: bootloader: Add orangepi-r1-plus-lts-rk3328 bootloader Herman Rimm via Guix-patches via
2023-12-01 19:50 ` Vagrant Cascadian
2023-11-18 16:01 ` [bug#67261] [PATCH 3/3] images: Add orangepi-r1-plus-lts image Herman Rimm via Guix-patches via
2023-12-01 19:58 ` Vagrant Cascadian
2023-12-03 10:22 ` Efraim Flashner
2023-12-22 23:59 ` Vagrant Cascadian
2023-11-27 8:33 ` [bug#67261] [PATCH v2] gnu: u-boot: Update to 2023.10 Herman Rimm via Guix-patches via
2023-12-01 19:48 ` Vagrant Cascadian
2023-12-02 7:11 ` Lars-Dominik Braun
2023-12-23 0:19 ` Vagrant Cascadian [this message]
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=875y0p7otr.fsf@wireframe \
--to=vagrant@debian.org \
--cc=67261-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=herman@rimm.ee \
/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.