From: Vagrant Cascadian <vagrant@debian.org>
To: Herman Rimm <herman@rimm.ee>, 68530@debbugs.gnu.org
Cc: Petr Hodina <phodina@protonmail.com>,
Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#68530] [PATCH 2/2] gnu: Add u-boot-amlogic.
Date: Wed, 17 Jan 2024 11:13:19 -0800 [thread overview]
Message-ID: <87sf2vbwog.fsf@wireframe> (raw)
In-Reply-To: <5b7310aaa70a66eb3060d6f7cb0324b7eba0b30a.1705499841.git.herman@rimm.ee>
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
On 2024-01-17, Herman Rimm wrote:
> diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
> index 151b42210c..b354af06c8 100644
> --- a/gnu/packages/bootloaders.scm
> +++ b/gnu/packages/bootloaders.scm
> @@ -894,6 +894,8 @@ (define-public u-boot-tools
> (lambda* (#:key make-flags test-target #:allow-other-keys)
> (invoke "test/image/test-imagetools.sh")))
> ;; Only run full test suite on x86_64 systems, as many tests
> +
> +
> ;; assume x86_64.
> ,@(if (string-match "^x86_64-linux"
> (or (%current-target-system)
Is this whitespace change needed for some reason?
> @@ -1134,6 +1136,14 @@ (define*-public (make-u-boot-sunxi64-package board triplet scp-firmware
> (modify-inputs (package-inputs base)
> (append arm-trusted-firmware-sun50i-a64))))))
>
> +(define %u-boot-amlogic-description-64-bit
> + "This is a common 64-bit build of U-Boot for all 64-bit capable Amlogic s905x
> +variants.")
> +
> +(define-public u-boot-amlogic
> + (make-u-boot-package "p212" "aarch64-linux-gnu"
> + #:append-description %u-boot-amlogic-description-64-bit))
> +
This should be called u-boot-p212. There are numerous other potential
amlogic platforms...
Although, an even bigger issues is that amlogic platforms all to my
knowledge require some non-free components in order to sign the binaries
before installing them, see the documentation in u-boot sources:
doc/board/amlogic/p212.rst
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2024-01-17 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:47 [bug#68530] [PATCH 1/2] gnu: u-boot: Update to 2024.01.3 Herman Rimm via Guix-patches via
2024-01-17 13:59 ` [bug#68530] [PATCH 2/2] gnu: Add u-boot-amlogic Herman Rimm via Guix-patches via
2024-01-17 19:13 ` Vagrant Cascadian [this message]
2024-01-17 19:59 ` [bug#68530] [PATCH 1/2] gnu: u-boot: Update to 2024.01.3 Vagrant Cascadian
2024-01-18 16:03 ` Herman Rimm via Guix-patches via
2024-01-18 16:11 ` [bug#68530] [PATCH v2] gnu: u-boot: Update to 2024.01 Herman Rimm via Guix-patches via
2024-01-18 18:14 ` Vagrant Cascadian
2024-01-18 18:23 ` bug#68530: " 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=87sf2vbwog.fsf@wireframe \
--to=vagrant@debian.org \
--cc=68530@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=herman@rimm.ee \
--cc=phodina@protonmail.com \
/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).