summaryrefslogtreecommitdiff
path: root/34/bdd43736f607a642a9cd614d565e72072a2714
blob: 0f14908783d20ed8fc517e622b84a7f300ce9f1b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
Return-Path: <jgarzik@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 3DD7EB88
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  3 Jul 2015 10:55:33 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id EC8141D6
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri,  3 Jul 2015 10:55:31 +0000 (UTC)
Received: by wgqq4 with SMTP id q4so85388806wgq.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 03 Jul 2015 03:55:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=iO48Byi7QKE5ihf5BXUASDFr7tK9dQRdU22LQN1JJ80=;
	b=k7Feul3WZ6iWGO8N2YkOfc9opuOMXhGA1Ii8g5bOVByFOBbyZt0q2q4Bre9XaaOmBz
	vy0xr1UUegGTGXe2wS/LtA7bGaZikgAkMZLQX6GC5YnB0BjwmNgmSTxK4zEXvmB/aj3y
	5JzHDtzD7FzYluUJGMERWMM/B3WsqH1NtqDO1CJ9gcoqFrETTrsQRlo78A0ZjJ1Lu0h/
	7NaPaCIs9WBxdwjltmmPuX6yyhmbDNTB/ZQv36bE2dbmVHlpgXDSBfDcZ1zStDyHaGvA
	pw82gvmDrgWd4qAx2JNYsM+0gBdZdHjHZxxEgO0HKo29B8ch2Q80M+VUf1dayfxr67dh
	DgWQ==
MIME-Version: 1.0
X-Received: by 10.180.79.162 with SMTP id k2mr45914799wix.46.1435920930404;
	Fri, 03 Jul 2015 03:55:30 -0700 (PDT)
Received: by 10.28.140.196 with HTTP; Fri, 3 Jul 2015 03:55:30 -0700 (PDT)
In-Reply-To: <CAJ+8mEOrO3ZvKCiTsX7VzF5Lwug+QE7x+k2EP1nQeqzSuK7AtA@mail.gmail.com>
References: <F6C7E867-1CCA-4DFB-8A88-361316A76FC3@me.com>
	<CABssiCq5JZdkQNmZ1x8OhNYqVxQOPXWe0Ui7wL7dCK9yQe9AoQ@mail.gmail.com>
	<5595503D.2010608@phauna.org>
	<CAJ+8mEM-MfRTTTK6-QnrvVtC63N5DZL6PiWSxsqTNm0KSYo=KQ@mail.gmail.com>
	<8019E8A9-AADF-44FE-99BF-8E1CB740E4B7@me.com>
	<CAJ+8mEOrO3ZvKCiTsX7VzF5Lwug+QE7x+k2EP1nQeqzSuK7AtA@mail.gmail.com>
Date: Fri, 3 Jul 2015 06:55:30 -0400
Message-ID: <CADm_WcYJ0=cSMo3xB+zT6pmxX0y6_uKpRgn1Jkq997Siev0grw@mail.gmail.com>
From: Jeff Garzik <jgarzik@gmail.com>
To: Jeremy Rubin <jeremy.l.rubin.travel@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04374511fb80e80519f66456
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Defining a min spec
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jul 2015 10:55:33 -0000

--f46d04374511fb80e80519f66456
Content-Type: text/plain; charset=UTF-8

On Fri, Jul 3, 2015 at 1:33 AM, Jeremy Rubin <
jeremy.l.rubin.travel@gmail.com> wrote:

> Moxie looks fantastic! The reason I thought RISC-V was a good selection is
> the very active development community which is pushing the performance of
> the ISA implementations forward. Can you speak to the health of Moxie
> development? Ultimately, ensuring support for many open architectures would
> be preferable. Are there other reasonable open-source processors that you
> are aware of?
>
> I would be willing to work on a design a Bitcoin specific open-hardware
> processor, up to the FPGA bound, if this would be useful for this goal.
>

Moxie was designed to be small and efficient from the compiler standpoint.
As a side effect, it is easy to audit from a security perspective.  It
started life as a simulator + gcc compiler backend, and then later became
an FPGA implementation.

Moxie would benefit from focused effort in building out the hardware side
to be efficient on FPGA, developing and testing multi-core support and
related efforts.  This area is less mature and could use attention.  Start
at https://github.com/atgreen/moxiedev/tree/master/moxie/cores/moxie

In terms of other projects, there are many open source processor cores at
http://opencores.org

--f46d04374511fb80e80519f66456
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Jul 3, 2015 at 1:33 AM, Jeremy Rubin <span dir=3D"=
ltr">&lt;<a href=3D"mailto:jeremy.l.rubin.travel@gmail.com" target=3D"_blan=
k">jeremy.l.rubin.travel@gmail.com</a>&gt;</span> wrote:<br><div class=3D"g=
mail_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><d=
iv>Moxie looks fantastic! The reason I thought RISC-V was a good selection =
is the very active development community which is pushing the performance o=
f the ISA implementations forward. Can you speak to the health of Moxie dev=
elopment? Ultimately, ensuring support for many open architectures would be=
 preferable. Are there other reasonable open-source processors that you are=
 aware of?</div><div><br></div><div>I would be willing to work on a design =
a Bitcoin specific open-hardware processor, up to the FPGA bound, if this w=
ould be useful for this goal.=C2=A0</div></div><div class=3D""><div class=
=3D"h5"><div class=3D"gmail_extra"></div></div></div></blockquote></div><br=
></div><div class=3D"gmail_extra">Moxie was designed to be small and effici=
ent from the compiler standpoint.=C2=A0 As a side effect, it is easy to aud=
it from a security perspective.=C2=A0 It started life as a simulator + gcc =
compiler backend, and then later became an FPGA implementation.</div><div c=
lass=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Moxie would benef=
it from focused effort in building out the hardware side to be efficient on=
 FPGA, developing and testing multi-core support and related efforts.=C2=A0=
 This area is less mature and could use attention.=C2=A0 Start at=C2=A0<a h=
ref=3D"https://github.com/atgreen/moxiedev/tree/master/moxie/cores/moxie">h=
ttps://github.com/atgreen/moxiedev/tree/master/moxie/cores/moxie</a><br></d=
iv><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_extra">In terms of other projects, there are many open source p=
rocessor cores at=C2=A0<a href=3D"http://opencores.org">http://opencores.or=
g</a></div><div class=3D"gmail_extra"><br></div></div></div>

--f46d04374511fb80e80519f66456--