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
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
|
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<style type="text/css">
@import url('../css/main.css');
</style>
<title>ASUS Chromebook C201</title>
</head>
<body>
<div class="section">
<h1 id="pagetop">ASUS Chromebook C201</h1>
<p>
This is a Chromebook, using the Rockchip RK3288 SoC. It uses
an ARM CPU, and has free EC firmware (unlike some other laptops).
More RK3288-based laptops will be added to libreboot at a later date.
</p>
<p>
Paul Kocialkowski, a <a href="http://www.replicant.us/">Replicant</a> developer, ported this laptop to libreboot. Thank you, Paul!
</p>
<p>
<b>More info will be added later, including build/installation instructions.
The board is supported in libreboot, however, and has been confirmed to work.</b>
</p>
<p>
Flashing instructions can be found at <a href="../install/index.html#flashrom">../install/index.html#flashrom</a>
</p>
<p>
<a href="index.html">Back to previous index</a>.
</p>
</div>
<div class="section">
<ul>
<li><a href="#googlesintent">Google's intent with CrOS devices</a></li>
<li><a href="#os">Considerations about ChromeOS and free operating systems</a></li>
<li><a href="#videoblobs">Caution: Video acceleration requires a non-free blob, software rendering can be used instead.</a></li>
<li><a href="#wifiblobs">Caution: WiFi requires a non-free blob, a USB dongle can be used instead.</a></li>
<li><a href="#ec">EC firmware is free software!</a></li>
<li><a href="#microcode">No microcode!</a></li>
<li><a href="#depthcharge">Depthcharge payload</a></li>
<li><a href="#thescrew">Flash chip write protection: the screw</a></li>
</ul>
</div>
<div class="section">
<h1 id="googlesintent">Google's intent with CrOS devices</h1>
<p>
CrOS (Chromium OS/Chrome OS) devices, such as Chromebooks, were not designed with the intent of bringing more freedom to users.
However, they run with a lot of free software at the boot software and embedded controller levels,
since free software gives Google enough flexibility to optimize various aspects such as boot time
and most importantly, to implement the CrOS security system, that involves various aspects of the software.
Google does hire a lot of Coreboot developers, who are generally friendly to the free software movement
and try to be good members of the free software community, by contributing code back.
</p>
<p>
CrOS devices are designed (from the factory) to actually coax the user into using
<a href="https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html">proprietary web services</a>
(SaaSS) that invade the user's privacy (ChromeOS is literally just the Google Chrome browser when you boot up, itself proprietary
and comes with proprietary add-ons like flash. It's only intended for SaaSS, not actual, real computing).
Google is even a member of the <i>PRISM</i> program, as outlined
by Edward Snowden. See notes about ChromeOS below. The libreboot project recommends
that the user replace the default <i>ChromeOS</i> with a distribution that can be used in freedom,
without invading the user's privacy.
</p>
<p>
We also use a similar argument for the MacBook and the ThinkPads that are supported in libreboot.
Those laptops are supported, in spite of Apple and Lenovo, companies which are actually <i>hostile</i>
to the free software movement.
</p>
<p>
<a href="#pagetop">Back to top of page</a>.
</p>
</div>
<div class="section">
<h1 id="os">Considerations about ChromeOS and free operating systems</h1>
<p>
This laptop comes preinstalled (from the factory) with Google ChromeOS. This is a GNU/Linux distribution, but it's not general purpose
and it comes with proprietary software. It's designed for <i><a href="https://www.gnu.org/philosophy/who-does-that-server-really-serve.en.html">SaaSS</a></i>. Libreboot recommends that users of this laptop replace it with another distribution.
</p>
<p>
Use one of the distributions recommend by the libreboot project.
See <a href="../distros/">../distros/</a>
</p>
<p>
<a href="#pagetop">Back to top of page</a>.
</p>
</div>
<div class="section">
<h1 id="videoblobs">Caution: Video acceleration requires a non-free blob, software rendering can be used instead.</h1>
<p>
The Tamil driver source code for the onboard Mali T GPU is not released. The developer has so-far withheld it. Until that is released, the only way to use video (in freedom) on this laptop is to not have video acceleration, by making sure not to install the relevant blob. Most tasks can still be performed without video acceleration, without any noticeable performance penalty.
</p>
<p>
In practise, this means that certain things like games, blender and GNOME shell (or other fancy desktops) won't work well.
The libreboot project recommends a lightweight desktop which does not need video acceleration, such as <i>XFCE</i> or <i>LXDE</i>.
</p>
<p>
The Tamil developer wrote this blog post, which sheds light on the story: <a href="http://libv.livejournal.com/27461.html">http://libv.livejournal.com/27461.html,http://libv.livejournal.com/27461.html</a>.
</p>
<p>
<a href="#pagetop">Back to top of page</a>.
</p>
</div>
<div class="section">
<h1 id="wifiblobs">Caution: WiFi requires a non-free blob, a USB dongle can be used instead.</h1>
<p>
These laptops have non-removeable (soldered on) WiFi chips, which require non-free firmware in the Linux kernel
in order to work.
</p>
<p>
The libreboot project recommends using an external USB wifi dongle that works
with free software. See <a href="index.html#recommended_wifi">index.html#recommended_wifi</a>.
</p>
<p>
There are 2 companies (endorsed by Creative Commons, under their <i>Respects your Freedom</i>
guidelines), that sell USB WiFi dongles guaranteed to work with free software (i.e. linux-libre kernel):
</p>
<ul>
<li><a href="https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb">ThinkPenguin sells them</a> (company based in USA)</li>
<li><a href="https://tehnoetic.com/tehnoetic-wireless-adapter-gnu-linux-libre-tet-n150">Tehnoetic sells them</a> (company based in Europe)</li>
</ul>
<p>
These wifi dongles use the AR9271 (atheros) chipset, supported by
the free <i>ath9k_htc</i> driver in the Linux kernel. They work in <i>linux-libre</i> too.
</p>
</div>
<div class="section">
<h1 id="ec">EC firmware is free software!</h1>
<p>
It's free software. Google provides the source. Build scripts will be added later, with EC sources
provided in libreboot, and builds of the EC firmware.
</p>
<p>
This is unlike the other current libreboot laptops (Intel based). In practise, you can
(if you do without the video/wifi blobs, and replace ChromeOS with a distribution
that respects your freedom) be more free when using one of these laptops.
</p>
<p>
The libreboot FAQ briefly describes what an <i>EC</i> is:
<a href="http://libreboot.org/faq/#firmware-ec">http://libreboot.org/faq/#firmware-ec</a>
</p>
</div>
<div class="section">
<h1 id="microcode">No microcode!</h1>
<p>
Unlike x86 (e.g. Intel/AMD) CPUs, ARM CPUs do not use microcode, not even built in.
On the Intel/AMD based libreboot systems, there is still microcode in the CPU
(not considered problematic by the FSF, provided that it is reasonably trusted
to not be malicious, since it's part of the hardware and read-only), but we
exclude microcode updates (volatile updates which are uploaded at boot time by the boot firmware,
if present), which are proprietary software.
</p>
<p>
On ARM CPUs, the instruction set is implemented in circuitry, without microcode.
</p>
<p>
<a href="#pagetop">Back to top of page</a>.
</p>
</div>
<div class="section">
<h1 id="depthcharge">Depthcharge payload</h1>
<p>
These systems do not use the GRUB payload. Instead, they use a payload called depthcharge,
which is common on CrOS devices. This is free software, maintained by Google.
</p>
</div>
<div class="section">
<h1 id="thescrew">Flash chip write protection: the screw</h1>
<p>
It's next to the flash chip. Unscrew it, and the flash chip is read-write. Screw it back in, and the flash chip is read-only.
It's called the screw.
</p>
<p>
<i>The screw</i> is accessible by removing other screws and gently prying off the upper shell, where the flash chip and the screw
are then directly accessible. User flashing from software is possible, without having to externally re-flash, but the flash chip
is SPI (SOIC-8 form factor) so you can also externally re-flash if you want to. In practise, you only need to externally re-flash
if you brick the laptop; read <a href="../install/bbb_setup.html">../install/bbb_setup.html</a> for an example of how to set up
an SPI programmer.
</p>
<p>
Write protection is useful, because it prevents the firmware from being re-flashed by any malicious software that
might become executed on your GNU/Linux system, as root. In other words, it can prevent a firmware-level <i>evil maid</i> attack. It's
possible to write protect on all current libreboot systems, but CrOS devices make it easy. The screw is such a stupidly
simple idea, which all designs should implement.
</p>
</div>
<div class="section">
<p>
Copyright © 2015 Leah Rowe <info@minifree.org><br/>
Permission is granted to copy, distribute and/or modify this document
under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license
or any later version published by Creative Commons;
A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a>
</p>
<p>
Updated versions of the license (when available) can be found at
<a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a>
</p>
<p>
UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
</p>
<p>
TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
</p>
<p>
The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
</p>
</div>
</body>
</html>
|
