unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: David Larsson <david.larsson@selfhosted.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org, help-guix@gnu.org, 33190-done@debbugs.gnu.org
Subject: Re: bug#33190: Choose devices according to linux-libre code
Date: Thu, 22 Nov 2018 12:15:41 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.21.9999.1811221213430.12650@localhost> (raw)
In-Reply-To: <87h8g9cvfy.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

Here's a list of places where you can get hardware that should be
compatible:
   * [[https://shop.libiquity.com/product/taurinus-x200|Libiquiti]]
   * [[https://minifree.org/|Minifree]]
   * [[https://tehnoetic.com/|Tehnoetic]]
   * [[https://store.vikings.net/|Vikings]]
   * [[https://puri.sm/products/|Purism]]

--
HTH
David Larsson

On Thu, 22 Nov 2018, Ludovic Courtès wrote:

> Hello,
>
> <znavko@tutanota.com> skribis:
>
>> As I've got here
>> https://lists.gnu.org/archive/html/help-guix/2018-10/msg00083.html
>> some devices cannot work without linux-firmware, requiring non-free
>> software drivers. It is so bad.
>>
>> I believe the issue can be solved by choosing devices that have proper
>> support by linux-libre code. So how to do this? Is there any info how
>> to choose devices working nice on linux-libre?
>
> The manual gives a couple of hints:
>
>  https://www.gnu.org/software/guix/manual/en/html_node/Hardware-Considerations.html
>
> The problem is of course not specific to GuixSD, that’s why the manual
> refers to H-Node, but there are probably other similar resources out
> there.
>
> HTH,
> Ludo’.
>
>
>

      parent reply	other threads:[~2018-11-22 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 18:45 Choose devices according to linux-libre code znavko
2018-10-30  9:56 ` bug#33190: " swedebugia
2018-11-22  9:28 ` Ludovic Courtès
     [not found] ` <87h8g9cvfy.fsf@gnu.org>
2018-11-22 11:15   ` David Larsson [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=alpine.LNX.2.21.9999.1811221213430.12650@localhost \
    --to=david.larsson@selfhosted.xyz \
    --cc=33190-done@debbugs.gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=ludo@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).