From: Brian Woodcox <bw@InSkyData.com>
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>,
Grant Wilson II <grantm.wilsonii@gmail.com>,
help-guix@gnu.org
Subject: Re: Pinebook pro build
Date: Mon, 19 Apr 2021 21:40:12 -0600 [thread overview]
Message-ID: <71807138-2885-4996-B19E-C148CA3CBBC1@InSkyData.com> (raw)
In-Reply-To: <YH42OlzbIDr/seGx@jasmine.lan>
Hi All,
I was able to create an image to run on the PineBook Pro —> https://lists.gnu.org/archive/html/guix-patches/2020-04/msg01101.html <https://lists.gnu.org/archive/html/guix-patches/2020-04/msg01101.html>
I haven’t updated this lately, but I have it running on 4 PineBook Pro’s. I hope it might help you out.
Brian.
> On Apr 19, 2021, at 8:02 PM, Leo Famulari <leo@famulari.name> wrote:
>
> On Mon, Apr 19, 2021 at 06:10:01PM -0700, Vagrant Cascadian wrote:
>> I should also mention that arm-trusted-firmware and u-boot packages have
>> support for cross-building when not using --target=ARCH. e.g. Building
>> these packages on x86_64 builds working binaries for the aarch64 boot
>> firmware.
>
> Oooh, that's good to know!
prev parent reply other threads:[~2021-04-20 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 20:06 Pinebook pro build Grant Wilson II
2021-04-18 23:03 ` Leo Famulari
2021-04-18 23:27 ` Grant Wilson II
2021-04-19 4:03 ` Leo Famulari
2021-04-19 22:55 ` Vagrant Cascadian
2021-04-20 0:24 ` Leo Famulari
2021-04-20 7:26 ` Efraim Flashner
2021-04-24 8:44 ` Vincent Legoll
2021-04-20 1:10 ` Vagrant Cascadian
2021-04-20 2:02 ` Leo Famulari
2021-04-20 3:40 ` Brian Woodcox [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
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=71807138-2885-4996-B19E-C148CA3CBBC1@InSkyData.com \
--to=bw@inskydata.com \
--cc=grantm.wilsonii@gmail.com \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
--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.
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).