From: Nils Gillmann <ng0@n0.is>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org, Joshua Branson <jbranso@fastmail.com>
Subject: Re: Librem
Date: Wed, 9 May 2018 16:58:49 +0000 [thread overview]
Message-ID: <20180509165849.q3on4zcv3nxtc74h@abyayala> (raw)
In-Reply-To: <87k1sd1hww.fsf@gmail.com>
Chris Marusich transcribed 2.5K bytes:
> Pierre Neidhardt <ambrevar@gmail.com> writes:
>
> >> https://www.raptorcs.com/TALOSII/
> >
> > Nice! I was originally referring to laptops only, but since I was
> > planning to look into desktops soon, so thanks for chiming in!
> >
> > It's waaaaaay too expensive for my needs though ;) Would you also happen
> > to know of libre desktop hardware in the 500-1000€ price range?
>
> It's true that the TALOSII costs more than your average consumer-grade
> desktop. However, I like the fact that they seem to put a strong focus
> on empowering the desktop owner to control their own computing by
> freeing as much software as possible. For example, they use OpenBMC,
> and a lot of the firmware used in the system is apparently available as
> free software:
>
> https://git.raptorcs.com/git/
>
> But it is expensive. :-) I haven't bought one yet, myself. Depending
> on your needs, I've heard you can put together a pretty good Libreboot
> desktop system for between 500 and 1000 US dollars, if you order and
> assemble the parts yourself.
The coreboot systems I have, and the small amount of the libreboot systems,
range between 100 Euro and 250 Euro (excluding the ~100? Euro I paid for the
flashing equipment).
> For me, "pretty good" means about 16 GiB
> of RAM, 8 CPU cores, and an SSD, since I'm mainly interested in generic
> development work (need those cores to build stuff in parallel!). But I
> haven't tried assembling my own Libreboot desktop yet, either. I would
> love to hear more from people who have!
>
> For a Libreboot-enabled system, you might also consider asking the
> Libreboot IRC chat room for help (last I heard, their email list was not
> working). I'm sure they can make some good recommendations!
>
> --
> Chris
next prev parent reply other threads:[~2018-05-09 16:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 17:25 Installation: Load non-free wifi firmware (iwlwifi) Pierre Neidhardt
2018-03-02 17:41 ` Pierre Neidhardt
2018-03-02 20:13 ` Carlo Zancanaro
2018-03-02 18:04 ` Adonay Felipe Nogueira
2018-03-05 12:32 ` Adonay Felipe Nogueira
2018-03-05 14:00 ` Clément Lassieur
2018-03-23 13:29 ` Pierre Neidhardt
2018-03-25 5:34 ` Chris Marusich
2018-03-25 6:14 ` Pierre Neidhardt
2018-03-25 10:21 ` Hartmut Goebel
2018-03-27 9:45 ` Ludovic Courtès
2018-03-27 22:05 ` Mark H Weaver
2018-04-13 11:55 ` Hartmut Goebel
2018-03-25 10:57 ` Marius Bakke
2018-03-29 5:11 ` Chris Marusich
2018-05-01 19:30 ` Librem (was: Installation: Load non-free wifi firmware (iwlwifi)) Pierre Neidhardt
2018-05-02 18:07 ` Librem Joshua Branson
2018-05-03 6:47 ` Librem Chris Marusich
2018-05-03 7:44 ` Librem Pierre Neidhardt
2018-05-09 6:07 ` Librem Chris Marusich
2018-05-09 16:58 ` Nils Gillmann [this message]
2018-05-04 20:56 ` Librem Joshua Branson
2018-05-04 15:15 ` Librem (was: Installation: Load non-free wifi firmware (iwlwifi)) Christopher Lemmer Webber
2018-05-04 15:17 ` Pierre Neidhardt
2018-05-04 16:32 ` Librem Mike Gerwitz
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=20180509165849.q3on4zcv3nxtc74h@abyayala \
--to=ng0@n0.is \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=jbranso@fastmail.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.
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).