unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Craven <david@craven.ch>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
	Christopher Howard <christopher@alaskasi.com>,
	Workgroup for fully free GNU/Linux distributions
	<gnu-linux-libre@nongnu.org>
Subject: Re: [GNU-linux-libre] Free firmware - A redefinition of the term and a new metric for it's measurement.
Date: Tue, 14 Feb 2017 11:41:24 +0100	[thread overview]
Message-ID: <CAL1_imkyCN6jmTfN9cESKAut3bX74ySq-=+LMhmLg6JxGNB9cg@mail.gmail.com> (raw)
In-Reply-To: <87inod2rd4.fsf@gmail.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.

It's more than a microcontroller chip design. The people behind sifive are
from uc berkeley and also developed a full gcc toolchain backend, a linux
port, a qemu and a clang port.

They have taped out multiple chips capable of booting Linux, and are
still working on putting the finishing touches on the privileged architecture
spec which is an open collaborative effort of the RISCV foundation, before
releasing their SoC.. The sifive developers play an important role there.

Benchmarks for code size and performance show that their SoC and the
ISA they developed is comparable to and out performs at least all ARM
cortex-a chips with an in-order-pipeline.

They also are developing and have taped out an out-of-order core. All of
their developments are released as free hardware.

Their specifications have enabled me to study a real world instruction set
architecture, studying something like ARM or x86 - I'm sure people have
looked at those manuals - are not something a beginner can study to
any form of completeness, they are simply to large and too complicated.

Cheers,
David

  reply	other threads:[~2017-02-14 10:41 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
2017-02-14 10:41                     ` David Craven [this message]
2017-02-14 17:47                       ` [GNU-linux-libre] " 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

  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='CAL1_imkyCN6jmTfN9cESKAut3bX74ySq-=+LMhmLg6JxGNB9cg@mail.gmail.com' \
    --to=david@craven.ch \
    --cc=christopher@alaskasi.com \
    --cc=gnu-linux-libre@nongnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.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.
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).