From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Pinebook Pro U-Boot: update to 2020.10, TF-A 2.3
Date: Sun, 14 Mar 2021 21:04:52 +0100 [thread overview]
Message-ID: <20210314200452.8rV90366CjE6B1_JIxgm5Hmf1kum7V7x7QJCbuvewME@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21199@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/21199#issuecomment-798970645
Comment:
> @ericonr this still LGTM. You would likely want somebody to create and test an image with mklive using this branch if you want to be safe. But nothing gets flashed to the bootloader partitions without the user doing it, so impact to running systems is low.
I just re-setup my pinebook with it, the image created from this did boot fine (the path in `mkimage.sh.in` just needed to be fixed).
next prev parent reply other threads:[~2021-03-14 20:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 9:57 [PR PATCH] Pinebook Pro U-Boot: use newer ARM Trusted Firmware CameronNemo
2020-09-07 6:10 ` [PR PATCH] [Updated] " CameronNemo
2020-09-11 15:55 ` [PR REVIEW] " sgn
2020-09-11 19:36 ` CameronNemo
2020-09-11 19:37 ` CameronNemo
2020-10-06 3:43 ` [PR PATCH] [Updated] " CameronNemo
2020-10-06 3:58 ` [PR REVIEW] " CameronNemo
2020-10-06 4:00 ` CameronNemo
2020-10-06 10:30 ` [PR REVIEW] Pinebook Pro U-Boot: update to 2020.10, TF-A 2.3 pullmoll
2020-10-27 3:05 ` [PR PATCH] [Updated] " CameronNemo
2020-11-21 23:43 ` CameronNemo
2020-11-22 19:42 ` CameronNemo
2021-02-16 5:46 ` ericonr
2021-02-16 7:15 ` CameronNemo
2021-02-16 7:16 ` CameronNemo
2021-03-14 20:04 ` Johnnynator [this message]
2021-03-15 18:41 ` [PR PATCH] [Closed]: " Johnnynator
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=20210314200452.8rV90366CjE6B1_JIxgm5Hmf1kum7V7x7QJCbuvewME@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).