summaryrefslogtreecommitdiff
path: root/talermerchantdemos/blog/articles/en/free-hardware-designs.html
diff options
context:
space:
mode:
Diffstat (limited to 'talermerchantdemos/blog/articles/en/free-hardware-designs.html')
-rw-r--r--talermerchantdemos/blog/articles/en/free-hardware-designs.html123
1 files changed, 74 insertions, 49 deletions
diff --git a/talermerchantdemos/blog/articles/en/free-hardware-designs.html b/talermerchantdemos/blog/articles/en/free-hardware-designs.html
index 9e862ea..3887189 100644
--- a/talermerchantdemos/blog/articles/en/free-hardware-designs.html
+++ b/talermerchantdemos/blog/articles/en/free-hardware-designs.html
@@ -1,24 +1,27 @@
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.90 -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
+<!--#set var="TAGS" value="essays aboutfs extension" -->
+<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
<title>Free Hardware and Free Hardware Designs
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/philosophy/po/free-hardware-designs.translist" -->
<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
+<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#include virtual="/server/top-addendum.html" -->
+<div class="article reduced-width">
<h2>Free Hardware and Free Hardware Designs</h2>
-<p>by <a href="http://www.stallman.org/">Richard M. Stallman</a></p>
-
-<!-- rms: I deleted the links because of Wired's announced
- anti-ad-block system -->
-<blockquote>
-<p>Most of this article was published in two parts in Wired in
-March 2015.</p>
-</blockquote>
+<address class="byline">by <a href="https://www.stallman.org/">Richard
+Stallman</a></address>
+<div class="introduction">
<p>To what extent do the ideas of free software extend to hardware?
Is it a moral obligation to make our hardware designs free, just as it
is to make our software free? Does maintaining our freedom require
rejecting hardware made from nonfree designs?</p>
+</div>
<h3 id="definitions">Definitions</h3>
@@ -53,7 +56,7 @@ means you can get a copy gratis. Many free programs are available for
zero price, since it costs you nothing to download your own copy, but
that's not what &ldquo;free&rdquo; means here. (In fact, some spyware
programs such as <a
-href="/philosophy/proprietary/proprietary-surveillance.html">Flash
+href="/proprietary/proprietary-surveillance.html">Flash
Player and Angry Birds</a> are gratis although they are not free.)
Saying &ldquo;libre&rdquo; along with &ldquo;free&rdquo; helps clarify
the point.</p>
@@ -69,7 +72,7 @@ denies freedom to its users is worth less than nothing.</p>
<p>We can use the term &ldquo;libre hardware&rdquo; as a concise
equivalent for &ldquo;hardware made from a free (libre)
-design&rdquo;.</p>
+design.&rdquo;</p>
<p>The terms &ldquo;open hardware&rdquo; and &ldquo;open source
hardware&rdquo; are used by some with the same concrete meaning as
@@ -113,10 +116,22 @@ consequences.</p>
<p>There is a gray area between hardware and software that contains
firmware that <em>can</em> be upgraded or replaced, but is not meant
-ever to be upgraded or replaced once the product is sold. In
-conceptual terms, the gray area is rather narrow. In practice, it is
-important because many products fall in it. We can treat that
-firmware as hardware with a small stretch.</p>
+ever to be upgraded or replaced once the product is sold. Or perhaps
+it is possible but unusual, or the manufacturer can release a
+replacement but you can't. In conceptual terms, the gray area is
+rather narrow. In practice, it is important because many products
+fall in it. Indeed, nowadays keyboards, cameras, disk drives and USB
+memories typically contain an embedded nonfree program that could be
+replaced by the manufacturer.</p>
+
+<p>We can treat that firmware as hardware with a small stretch, but we
+must not try to have it both ways. If we treat certain firmware as
+impossible to change, since it is not realistically possible to avoid
+that firmware, we must also treat it as impossible to change when we
+might wish it could be changed. That entails refusing all upgrades or
+patches to that firmware. That is what I do, and this is the reason I
+do it. Until we can get computers with entirely free firmware, there
+is no feasible way to do better than this.</p>
<p>Some have said that preinstalled firmware programs and
Field-Programmable Gate Array chips (FPGAs) &ldquo;blur the boundary
@@ -135,8 +150,9 @@ gate pattern file that gets loaded into the FPGA is secret. For many
years there was no model of FPGA for which those files could be
produced without nonfree (proprietary) tools.</p>
-<p>As of 2015, free software tools are available for
-<a href="http://www.clifford.at/icestorm/">programming the Lattice
+<p>As of 2015, free software tools are available for <a
+href="https://web.archive.org/web/20211106213411/http://www.clifford.at/icestorm/">
+programming the Lattice
iCE40</a>, a common model of FPGA, from input written in a hardware
description language (HDL). It is also possible to compile C programs
and run them on the Xilinx Spartan 6 LX9 FPGA
@@ -167,15 +183,15 @@ program.</p>
<p>Be careful to choose 3D printers that work with exclusively free
software; the Free Software Foundation <a
-href="http://fsf.org/resources/hw/endorsement">endorses such
+href="https://ryf.fsf.org/">endorses such
printers</a>. Some 3D printers are made from free hardware designs,
but <a
-href="http://www.cnet.com/news/pulling-back-from-open-source-hardware-makerbot-angers-some-adherents/">Makerbot's
+href="https://www.cnet.com/tech/tech-industry/pulling-back-from-open-source-hardware-makerbot-angers-some-adherents/">Makerbot's
hardware designs are nonfree</a>.</p>
<h3 id="reject-nonfree">Must We Reject Nonfree Digital Hardware?</h3>
-<p>Is a nonfree digital <a href="#fn1">(*)</a> hardware design an
+<p>Is a nonfree digital <a href="#fn1">[1]</a> hardware design an
injustice? Must we, for our freedom's sake, reject all digital
hardware made from nonfree designs, as we must reject nonfree
software?</p>
@@ -213,8 +229,8 @@ computer. Constructing a big circuit is a lot of painstaking work,
and that's once you have the circuit board. Fabricating a chip is not
feasible for individuals today; only mass production can make them
cheap enough. With today's hardware technology, users can't download
-and run John H Hacker's modified version of a digital hardware design,
-as they could run John S Hacker's modified version of a program.
+and run a modified version of a widely used digital hardware design,
+as they could run a modified version of a widely used program.
Thus, the four freedoms don't give users today collective control over
a hardware design as they give users collective control over a
program. That's where the reasoning showing that all software must be
@@ -242,12 +258,6 @@ software will then apply to nonfree hardware designs too.</p>
<p>That future is years away, at least. In the meantime, there is no
need to reject hardware with nonfree designs on principle.</p>
-<hr />
-
-<p id="fn1">* As used here, &ldquo;digital hardware&rdquo; includes
-hardware with some analog circuits and components in addition to
-digital ones.</p>
-
<h3 id="free-designs">We Need Free Digital Hardware Designs</h3>
<p>Although we need not reject digital hardware made from nonfree
@@ -323,9 +333,9 @@ ideal future we will want the design be free at all levels. Under
present circumstances, just making one level free is a significant
advance.</p>
-<p>However, if a design at one level combines free and nonfree parts
-&mdash; for example, a &ldquo;free&rdquo; HDL circuit that
-incorporates proprietary &ldquo;soft cores&rdquo; &mdash; we must
+<p>However, if a design at one level combines free and nonfree
+parts&mdash;for example, a &ldquo;free&rdquo; HDL circuit that
+incorporates proprietary &ldquo;soft cores&rdquo;&mdash;we must
conclude that the design as a whole is nonfree at that level.
Likewise for nonfree &ldquo;wizards&rdquo; or &ldquo;macros,&rdquo; if
they specify part of the interconnections of chips or programmably
@@ -367,9 +377,9 @@ from the drawing. As far as copyright is concerned, everyone is free
to make them and use them (and that's a freedom we need very much).
In the US, copyright does not cover the functional aspects that the
design describes, but <a
-href="http://www.copyright.gov/title17/92chap13.html#1301">does cover decorative
+href="https://www.copyright.gov/title17/92chap13.html#1301">does cover decorative
aspects</a>. When one object has decorative aspects and functional
-aspects, you get into tricky ground <a href="#fn2">(*)</a>.</p>
+aspects, you get into tricky ground <a href="#fn2">[2]</a>.</p>
<p>All this may be true in your country as well, or it may not.
Before producing objects commercially or in quantity, you should
@@ -384,16 +394,6 @@ common. This is why the term &ldquo;<a
href="/philosophy/not-ipr.html">intellectual property</a>&rdquo; is
pure confusion and should be totally rejected.</p>
-<hr />
-
-<p id="fn2">* An article by Public Knowledge gives useful information
-about this <a
-href="https://www.publicknowledge.org/assets/uploads/documents/3_Steps_for_Licensing_Your_3D_Printed_Stuff.pdf">
-complexity</a>, for the US, though it falls into the common mistake of
-using the bogus concept of &ldquo;intellectual property&rdquo; and the
-propaganda term &ldquo;<a
-href="/philosophy/words-to-avoid.html#Protection">protection</a>.&rdquo;</p>
-
<h3 id="promoting">Promoting Free Hardware Designs Through Repositories</h3>
<p>The most effective way to push for published hardware designs to be
@@ -419,7 +419,7 @@ or any of the CC licenses.</p>
<p>The repository should require all designs to be published as source
code, and source code in secret formats usable only by proprietary
design programs is not really adequate. For a 3D model, the <a
-href="http://en.wikipedia.org/wiki/STL_%28file_format%29">STL
+href="https://en.wikipedia.org/wiki/STL_%28file_format%29">STL
format</a> is not the preferred format for changing the design and
thus is not source code, so the repository should not accept it,
except perhaps accompanying real source code.</p>
@@ -442,10 +442,35 @@ manufacturer.</p>
free. What we need is to recognize as a community that this is what
we should do and to insist on free designs when we fabricate objects
ourselves.</p>
+<div class="column-limit"></div>
+
+<h3 class="footnote">Footnotes</h3>
+<ol>
+<li id="fn1">As used here, &ldquo;digital hardware&rdquo; includes
+hardware with some analog circuits and components in addition to
+digital ones.</li>
+
+<li id="fn2">An article by Public Knowledge gives useful information
+about this <a
+href="https://web.archive.org/web/20211203021432/https://www.publicknowledge.org/assets/uploads/documents/3_Steps_for_Licensing_Your_3D_Printed_Stuff.pdf">
+complexity</a>, for the US, though it falls into the common mistake of
+using the bogus concept of &ldquo;intellectual property&rdquo; and the
+propaganda term &ldquo;<a
+href="/philosophy/words-to-avoid.html#Protection">protection</a>.&rdquo;</li>
+</ol>
+
+<!-- rms: I deleted the links because of Wired's announced
+ anti-ad-block system -->
+<div class="infobox extra" role="complementary">
+<hr />
+<p>Most of this article was published in two parts in <cite>Wired</cite> in
+March 2015.</p>
+</div>
+</div>
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
-<div id="footer">
+<div id="footer" role="contentinfo">
<div class="unprintable">
<p>Please send general FSF &amp; GNU inquiries to
@@ -463,13 +488,13 @@ to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
to <a href="mailto:web-translators@gnu.org">
&lt;web-translators@gnu.org&gt;</a>.</p>
- <p>For information on coordinating and submitting translations of
+ <p>For information on coordinating and contributing translations of
our web pages, see <a
href="/server/standards/README.translations.html">Translations
README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting translations
+README</a> for information on coordinating and contributing translations
of this article.</p>
</div>
@@ -490,7 +515,7 @@ of this article.</p>
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2015, 2016, 2018, 2019 Richard Stallman</p>
+<p>Copyright &copy; 2015, 2021, 2022 Richard Stallman</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
@@ -500,7 +525,7 @@ Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2019/12/30 11:28:30 $
+$Date: 2022/03/05 13:35:13 $
<!-- timestamp end -->
</p>
</div>