From: Tobias Platen <guix@platen-software.de>
To: guix-devel@gnu.org
Subject: Re: Please review blog post draft: powerpc64le-linux support
Date: Sat, 10 Apr 2021 11:59:38 +0200 [thread overview]
Message-ID: <20210410115938.f97fe5b8c7abbf39fd3025c9@platen-software.de> (raw)
In-Reply-To: <42ef259583a7acc134f587a92c902a8ad6b4039c.camel@zaclys.net>
On Fri, 09 Apr 2021 00:59:44 +0200
Léo Le Bouter <lle-bout@zaclys.net> wrote:
> On Thu, 2021-04-08 at 09:37 -0700, Chris Marusich wrote:
> > They also say in that Twitter thread: "We have been putting together
> > our
> > systems from blob-free components only (sans NIC as is known and
> > being
> > actively worked), and this is an area where no low-cost blob-free
> > silicon is available right now."
> >
>
> I've been using the Free Software firmware replacement for the NIC
> since a while now and it's working great:
> https://github.com/meklort/bcm5719-fw/
I've install that firmware on my Talos II and I can confirm that it works.
I have reviewed 0001-website-drafts-Add-powerpc64le-linux-announcement.patch and it looks good.
It would be good to mention the Libre-SoC project(https://libre-soc.org/), which might be a good target for the future.
Tobias
--
Sent from my IBM 7094
next prev parent reply other threads:[~2021-04-10 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 7:15 Please review blog post draft: powerpc64le-linux support Chris Marusich
2021-04-06 15:47 ` Joshua Branson
2021-04-08 5:46 ` Chris Marusich
2021-04-06 23:13 ` Léo Le Bouter
2021-04-08 6:04 ` Chris Marusich
2021-04-08 8:55 ` Chris Marusich
2021-04-08 10:49 ` Vincent Legoll
2021-04-08 16:37 ` Chris Marusich
2021-04-08 17:15 ` Vincent Legoll
2021-04-08 22:59 ` Léo Le Bouter
2021-04-10 9:59 ` Tobias Platen [this message]
2021-04-11 7:34 ` Chris Marusich
2021-04-11 7:37 ` Chris Marusich
2021-04-12 19:46 ` Chris Marusich
2021-04-15 22:06 ` Léo Le Bouter
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=20210410115938.f97fe5b8c7abbf39fd3025c9@platen-software.de \
--to=guix@platen-software.de \
--cc=guix-devel@gnu.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).