diff options
author | Runxi Yu <me@runxiyu.org> | 2024-05-12 14:34:36 +0800 |
---|---|---|
committer | Runxi Yu <me@runxiyu.org> | 2024-05-12 14:34:36 +0800 |
commit | d1e870a7f871e3f6ef58d0ab6e3f73150cf8cf44 (patch) | |
tree | 119adf3578b2d56dd60df0432e7bf74cbaaff1cc /free-hardware.html | |
parent | a886af6628166343bfbed9837853c81fcdbeefe1 (diff) | |
download | www-d1e870a7f871e3f6ef58d0ab6e3f73150cf8cf44.tar.gz |
Spell check
Diffstat (limited to 'free-hardware.html')
-rw-r--r-- | free-hardware.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/free-hardware.html b/free-hardware.html index 3df32ef..ba710b6 100644 --- a/free-hardware.html +++ b/free-hardware.html @@ -17,7 +17,7 @@ <p>In fact, access to schematics, boardviews, datasheets and any other documentation is <em>critical</em> to software freedom.</p> <p>—Leah Rowe, founder and lead developer of <a href="https://libreboot.org">Libreboot</a></p> </blockquote> - <p>We can't make free software, especially bootloaders and operating systems, if we don't have knowledge of how hardware works. In modern day computing we do understand how to design kernels for most architectures such as x86 and aarch64, but this is not enough—without extensive research into how components in a specific peice of hardware interact with each other, we may be able to accomplish simple tasks such as running an OS on it, but <a href="https://www.fsf.org/campaigns/fight-to-repair">the right to repair</a> is severely restricted, and we can't check if the <em>hardware</em> is doing nasty things, or replace parts of it should it be so.</p> + <p>We can't make free software, especially bootloaders and operating systems, if we don't have knowledge of how hardware works. In modern day computing we do understand how to design kernels for most architectures such as x86 and aarch64, but this is not enough—without extensive research into how components in a specific piece of hardware interact with each other, we may be able to accomplish simple tasks such as running an OS on it, but <a href="https://www.fsf.org/campaigns/fight-to-repair">the right to repair</a> is severely restricted, and we can't check if the <em>hardware</em> is doing nasty things, or replace parts of it should it be so.</p> </div> <div id="what-is-free-hardware"> <h2>What are Free Hardware Designs?</h2> @@ -50,7 +50,7 @@ <p>If you're just a normal computer user, kindly ask the manufacturer of your hardware for design files and datasheets. Show manufacturer that you care about your freedom to hack the hardware.</p> <p>When considering purchasing new hardware, prioritize free hardware. At this stage it is extremely rare to find any, but still be on the lookout. Please, if you find any that seem to be trustworthy, tell the community about it.</p> <h3>Hardware manufacturers</h3> - <p>When you create a hardware design, use the <a href="https://www.gnu.org/licenses/gpl-3.0.txt">GNU General Public License, version 3</a> (please add "or later") or the <a href="https://ohwr.org/cern_ohl_s_v2.txt">CERN Open Hardware Licence Version 2 - Strongly Reciprocal</a> license! CERN 2.0 is a strong copyleft license for hardware designs, similar to the spirit of the GNU GPL, which is more widely used in free software. The GPL is not specifically designed for hardware designs, but it seems to be work for hardware designs, at least RMS's lawyers believe it's okay. CERN 2.0 is more complicated and has more legalese. However, since the GPL can acheive most of CERN, discussion is needed for which to use and whether letting yet another license proliferate is good. Using these licenses ensures that it is illegal to take your design and make proprietary hardware (or designs thereof) out of it.</p> + <p>When you create a hardware design, use the <a href="https://www.gnu.org/licenses/gpl-3.0.txt">GNU General Public License, version 3</a> (please add "or later") or the <a href="https://ohwr.org/cern_ohl_s_v2.txt">CERN Open Hardware Licence Version 2 - Strongly Reciprocal</a> license! CERN 2.0 is a strong copyleft license for hardware designs, similar to the spirit of the GNU GPL, which is more widely used in free software. The GPL is not specifically designed for hardware designs, but it seems to be work for hardware designs, at least RMS's lawyers believe it's okay. CERN 2.0 is more complicated and has more legalese. However, since the GPL can achieve most of CERN, discussion is needed for which to use and whether letting yet another license proliferate is good. Using these licenses ensures that it is illegal to take your design and make proprietary hardware (or designs thereof) out of it.</p> <p>If you're wondering how you could profit, see <a href="#faq-profit">the FAQ on profits</a>.</p> </div> <div id="faq"> |