From: Herman Rimm via Guix-patches via <guix-patches@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>, 68530@debbugs.gnu.org
Cc: Efraim Flashner <efraim@flashner.co.il>
Subject: [bug#68530] [PATCH 1/2] gnu: u-boot: Update to 2024.01.3.
Date: Thu, 18 Jan 2024 17:03:58 +0100 [thread overview]
Message-ID: <hbge7sk6tq7cnoivgxfyqdkmxho6usutnmdzxrsrjqq7fa5eof@vr3m3pgqwkbe> (raw)
In-Reply-To: <87jzo7buiu.fsf@wireframe>
On Wed, Jan 17, 2024 at 11:59:53AM -0800, Vagrant Cascadian wrote:
> These two commits were included in upstream git, which might be
> relevent or helpful?
>
> 03e598263e3878b6f5d58f5525577903edadc644 tools: fix build without LIBCRYPTO support
> b646a1053fda188bfb054acc98aa73bb23b158b1 tools: kwbimage: Allow disabling build on non-mvebu platforms
Nice find! I have included 03e5982 as a patch, which fixes the
u-boot-amlogic-p212 build errors.
> 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:
Yes, I think it would be more useful to add u-boot-amlogic-p212 and the
tools from #60043 to a non-official channel together with the non-free
stuff.
Cheers,
Herman
next prev parent reply other threads:[~2024-01-18 16:05 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
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 [this message]
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=hbge7sk6tq7cnoivgxfyqdkmxho6usutnmdzxrsrjqq7fa5eof@vr3m3pgqwkbe \
--to=guix-patches@gnu.org \
--cc=68530@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 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).