all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>,
	John Darrington <john@darrington.wattle.id.au>,
	Workgroup for fully free GNU/Linux distributions
	<gnu-linux-libre@nongnu.org>
Subject: Re: Free firmware - A redefinition of the term and a new metric for it's measurement.
Date: Mon, 13 Feb 2017 22:55:51 -0800	[thread overview]
Message-ID: <87inod2rd4.fsf@gmail.com> (raw)
In-Reply-To: <CAL1_imnUL51WCtVQ99FgiSa3AYdQNYSpL__6Ep087+7uXF9Kyw@mail.gmail.com> (David Craven's message of "Mon, 13 Feb 2017 20:24:33 +0100")

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

David Craven <david@craven.ch> writes:

>> If the attacker *is* vendor who supplies the proprietary device then they would
>> not have to reverse engineer it.
>
> You can always choose not to apply the vendors update. If for example
> the company you initially trusted with by purchasing their device gets
> bought by another company or you have some other reason to stop
> trusting it. CEO changed, their website was hacked or whatever.
>

Either ways, as long as it's opaque, either shipped in a (semi) fixed
state or loaded at runtime, it's not auditable, so there's nothing too
interesting to be discussed in regards of trust or freedom. The later at
least doesn't clutter our view (and the Linux git tree) -- blobs have
grown from ~10 MiB in Linux 2.6.33 [0] to 158 MiB (du -sh on a checkout of
the the linux-firmware git tree [1] (pruned from its .git))

>> A recommended read for anyone interested in the idea of free hardware!
>> Thanks for sharing.
>
> Don't know if you've heard of sifive [0]. If there is a startup that
> has the potential to create lasting change in the semiconductor
> industry, my money is on them... :) I should be getting one of the
> first riscv boards soon!
>
> [0] https://www.sifive.com/

I had followed some earlier developments but had lost track recently!
I'm happy to see that they have released the sources of their
microcontroller chip design. Apparently the design (Apache licensed) is
described using a tool/language called Chisel, which is Scala based and
can generate two flavors of Verilog as well as a C++ version for
simulation purposes. Interesting times!

Maxim

[0] https://www.fsfla.org/ikiwiki/anuncio/2010-03-Linux-2.6.33-libre.en
[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-02-14  6:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 14:37 Free firmware - A redefinition of the term and a new metric for it's measurement David Craven
2017-02-03 17:40 ` Taylan Ulrich Bayırlı/Kammer
2017-02-03 18:18   ` David Craven
2017-02-03 18:44     ` Christopher Howard
2017-02-03 20:12       ` David Craven
2017-02-05 22:53       ` [GNU-linux-libre] " Maxim Cournoyer
2017-02-10 17:31         ` David Craven
2017-02-10 18:21           ` Christopher Howard
2017-02-13  7:02             ` Maxim Cournoyer
2017-02-13  8:42               ` [GNU-linux-libre] " John Darrington
2017-02-13 19:24                 ` David Craven
2017-02-13 21:21                   ` [GNU-linux-libre] " Hartmut Goebel
2017-02-13 22:48                     ` David Craven
2017-02-14  6:55                   ` Maxim Cournoyer [this message]
2017-02-14 10:41                     ` David Craven
2017-02-14 17:47                       ` Maxim Cournoyer
2017-02-14 12:15 ` Denis 'GNUtoo' Carikli
2017-02-14 18:43   ` [GNU-linux-libre] " David Craven
2017-02-14 20:11     ` Adonay Felipe Nogueira
2017-02-14 20:47       ` David Craven
2017-02-14 20:57         ` Christopher Howard
2017-02-14 21:01           ` David Craven
2017-02-14 21:13             ` [GNU-linux-libre] " David Craven
2017-02-20  7:50     ` Denis 'GNUtoo' Carikli
2017-02-21 12:15       ` David Craven

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=87inod2rd4.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=david@craven.ch \
    --cc=gnu-linux-libre@nongnu.org \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.