From de26b8e8f2ffbed23eee9c3e07ebd4ea5f3b2c33 Mon Sep 17 00:00:00 2001
From: Francis Rowe <info@gluglug.org.uk>
Date: Wed, 23 Sep 2015 19:33:20 -0400
Subject: optimize css

---
(limited to 'site/faq/index.php')

diff --git a/site/faq/index.php b/site/faq/index.php
index b24a616..1e8d6d4 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -41,7 +41,7 @@
 				as time goes by. <a href="../">Back to home page</a>
 			</p>
 			<h2>Hardware compatibility</h2>
-				<ul class="cascade">
+				<ul class="c">
 					<li><a href="#compatibility">What systems are compatible with libreboot?</a></li>
 					<li>
 						<a href="#intel">Why is the latest Intel hardware unsupported in libreboot?</a>
@@ -60,7 +60,7 @@
 					<li><a href="#amd">What about AMD?</a></li>
 				</ul>
 			<h2>General questions</h2>
-				<ul class="cascade">
+				<ul class="c">
 					<li><a href="#install">How do I install libreboot?</a></li>
 					<li><a href="#repugnantpi">How do I program an SPI flash chip with the Raspberry Pi?</a></li>
 					<li><a href="#bootpassword">How do I set a boot password?</a></li>
@@ -70,7 +70,7 @@
 					<li><a href="#reinstallos">Do I need to re-flash when I re-install GNU/Linux?</a></li>
 				</ul>
 			<h2>Freedom questions</h2>
-				<ul class="cascade">
+				<ul class="c">
 					<li>
 						<a href="#otherfirmware">What other firmware exists outside of libreboot?</a>
 						<ul>
@@ -86,7 +86,7 @@
 					</li>
 				</ul>
 			<h2>Operating Systems</h2>
-				<ul class="cascade">
+				<ul class="c">
 					<li><a href="#gnulinux">Can I use GNU/Linux?</a> (yes, you can)</li>
 					<li><a href="#gnuhurd">Can I use GNU/Hurd?</a></li>
 					<li><a href="#bsd">Can I use BSD?</a></li>
@@ -99,7 +99,7 @@
 	<div>
 		<h1>Hardware compatibility</h1>
 
-			<h2 id="compatibility">What systems are compatible with libreboot? <span class="ref">(<a href="#compatibility">#compatibility</a>)</span></h2>
+			<h2 id="compatibility">What systems are compatible with libreboot? <span class="r"><a href="#compatibility">#compatibility</a></span></h2>
 				<p>
 					See <a href="../docs/hcl/index.html">../docs/hcl/index.html</a>.
 				</p>
@@ -111,13 +111,13 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="intel">Why is the latest Intel hardware unsupported in libreboot? <span class="ref">(<a href="#intel">#intel</a>)</span></h2>
+			<h2 id="intel">Why is the latest Intel hardware unsupported in libreboot? <span class="r"><a href="#intel">#intel</a></span></h2>
 				<p>
 					It is extremely unlikely that any post-2008 Intel hardware will ever be supported in libreboot, due to
 					severe security and freedom issues; so severe, that <i>the libreboot project recommends avoiding all modern Intel hardware.
 					If you have an Intel based system affected by the problems described below, then you should get rid of it as soon as possible</i>. The main issues are as follows:
 				</p>
-				<h3 id="intelme">Intel Management Engine (ME) <span class="ref">(<a href="#intelme">#intelme</a>)</span></h3>
+				<h3 id="intelme">Intel Management Engine (ME) <span class="r"><a href="#intelme">#intelme</a></span></h3>
 					<p>
 						Introduced in June 2006 in Intel's 965 Express Chipset Family of (Graphics and)
 						Memory Controller Hubs, or (G)MCHs, and the ICH8 I/O Controller Family, the
@@ -256,7 +256,7 @@
 						Platform Embedded Security Technology Revealed</a></i></b> describes in great
 						detail the ME's hardware architecture and firmware application modules.
 					</p>
-				<h3 id="fsp">Firmware Support Package (FSP) <span class="ref">(<a href="#fsp">#fsp</a>)</span></h3>
+				<h3 id="fsp">Firmware Support Package (FSP) <span class="r"><a href="#fsp">#fsp</a></span></h3>
 					<p>
 						On all recent Intel systems, coreboot support has revolved around integrating a blob (for each system) called
 						the <i>FSP</i> (firmware support package), which handles all of the hardware initialization, including
@@ -269,7 +269,7 @@
 						perform a number of attacks on the user (the list is endless). Any Intel system that has the proprietary FSP blob cannot be trusted at
 						all.</b> In fact, several SMM rootkits have been demonstrated in the wild (use a search engine to find them).
 					</p>
-				<h3 id="microcode">CPU microcode updates <span class="ref">(<a href="#microcode">#microcode</a>)</span></h3>
+				<h3 id="microcode">CPU microcode updates <span class="r"><a href="#microcode">#microcode</a></span></h3>
 					<p>
 						All modern x86 CPUs (from Intel and AMD) use what is called <i>microcode</i>. CPUs are extremely complex,
 						and difficult to get right, so the circuitry is designed in a very generic way, where only basic instructions
@@ -295,7 +295,7 @@
 						you had the source code. If you try to upload your own modified updates, the CPU will reject them. In other words,
 						the microcode updates are <i><a href="https://www.gnu.org/proprietary/proprietary-tyrants.html">tivoized</a></i>.
 					</p>
-				<h3 id="intelbastards">Intel is uncooperative <span class="ref">(<a href="#intelbastards">#intelbastards</a>)</span></h3>
+				<h3 id="intelbastards">Intel is uncooperative <span class="r"><a href="#intelbastards">#intelbastards</a></span></h3>
 					<p>
 						For years, coreboot has been struggling against Intel. Intel has been shown to be extremely uncooperative in general.
 						Many coreboot developers, and companies, have tried to get Intel to cooperate; namely, releasing source code
@@ -324,7 +324,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="librem">Will the Purism Librem laptops be supported? <span class="ref">(<a href="#librem">#librem</a>)</span></h2>
+			<h2 id="librem">Will the Purism Librem laptops be supported? <span class="r"><a href="#librem">#librem</a></span></h2>
 				<p>
 					Probably not. There are several privacy, security and freedom issues with these laptops, due to the Intel chipsets
 					that they use. See <a href="#intel">#intel</a>. There are signed proprietary blobs which cannot be replaced
@@ -347,7 +347,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="thinkpads">Will the latest ThinkPad models be supported? <span class="ref">(<a href="#thinkpads">#thinkpads</a>)</span></h2>
+			<h2 id="thinkpads">Will the latest ThinkPad models be supported? <span class="r"><a href="#thinkpads">#thinkpads</a></span></h2>
 				<p>
 					The latest ThinkPad generation supported in libreboot are the ones
 					using the GM45 (ICH9) chipsets, such as the ThinkPad X200 or T400.
@@ -364,7 +364,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="desktops">Will desktop/server hardware be supported? <span class="ref">(<a href="#desktops">#desktops</a>)</span></h2>
+			<h2 id="desktops">Will desktop/server hardware be supported? <span class="r"><a href="#desktops">#desktops</a></span></h2>
 				<p>
 					A common issue with desktop hardware is the Video BIOS. Libreboot has to initialize the graphics chipset,
 					but most graphics cards lack a free Video BIOS for this purpose. Some desktop motherboards supported in
@@ -387,7 +387,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="randomhardware">Hi, I have &lt;insert random system here&gt;, is it supported? <span class="ref">(<a href="#randomhardware">#randomhardware</a>)</span></h2>
+			<h2 id="randomhardware">Hi, I have &lt;insert random system here&gt;, is it supported? <span class="r"><a href="#randomhardware">#randomhardware</a></span></h2>
 				<p>
 					Most likely not. First, you must consult coreboot's own hardware compatibility list
 					at <a href="http://www.coreboot.org/Supported_Motherboards">http://www.coreboot.org/Supported_Motherboards</a> and,
@@ -410,14 +410,14 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="arm">What about ARM? <span class="ref">(<a href="#arm">#arm</a>)</span></h2>
+			<h2 id="arm">What about ARM? <span class="r"><a href="#arm">#arm</a></span></h2>
 				<p>
 					TODO
 				</p>
 				<p>
 					<a href="#pagetop">Back to top of page</a>
 				</p>
-			<h2 id="amd">What about AMD? <span class="ref">(<a href="#amd">#amd</a>)</span></h2>
+			<h2 id="amd">What about AMD? <span class="r"><a href="#amd">#amd</a></span></h2>
 				<p>
 					Libreboot has support for some AMD platforms, with more on the horizon.
 					See <a href="../docs/hcl/index.html">../docs/hcl/index.html</a>.
@@ -433,7 +433,7 @@
 	<div>
 		<h1>General questions</h1>
 
-			<h2 id="install">How do I install libreboot? <span class="ref">(<a href="#install">#install</a>)</span></h2>
+			<h2 id="install">How do I install libreboot? <span class="r"><a href="#install">#install</a></span></h2>
 				<p>
 					See <a href="../docs/install/index.html">../docs/install/index.html</a>
 				</p>
@@ -441,7 +441,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="repugnantpi">How do I program an SPI flash chip with the Raspberry Pi? <span class="ref">(<a href="#repugnantpi">#repugnantpi</a>)</span></h2>
+			<h2 id="repugnantpi">How do I program an SPI flash chip with the Raspberry Pi? <span class="r"><a href="#repugnantpi">#repugnantpi</a></span></h2>
 				<p>
 					The RPi can be used to install libreboot onto a system that uses SPI flash, but libreboot intentionally doesn't document it.
 					Why? Blobs. The RPi requires a blob for the integrated video chipset, in order to boot. This was true of the original RPi, and
@@ -455,7 +455,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="bootpassword">How do I set a boot password? <span class="ref">(<a href="#bootpassword">#bootpassword</a>)</span></h2>
+			<h2 id="bootpassword">How do I set a boot password? <span class="r"><a href="#bootpassword">#bootpassword</a></span></h2>
 				<p>
 					If you are using the GRUB payload, you can add a username and password (salted, hashed)
 					to your GRUB configuration that resides inside the flash chip. The following guides (which
@@ -466,7 +466,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="writeprotect">How do I write-protect the flash chip? <span class="ref">(<a href="#writeprotect">#writeprotect</a>)</span></h2>
+			<h2 id="writeprotect">How do I write-protect the flash chip? <span class="r"><a href="#writeprotect">#writeprotect</a></span></h2>
 				<p>
 					By default, there is no write-protection on a libreboot system. This is for usability reasons,
 					because most people do not have easy access to an external programmer for re-flashing their firmware,
@@ -487,7 +487,7 @@
 				<p>
 					<a href="#pagetop">Back to top of page</a>
 				</p>
-			<h2 id="biossettings">How do I change the BIOS settings? <span class="ref">(<a href="#biossettings">#biossettings</a>)</span></h2>
+			<h2 id="biossettings">How do I change the BIOS settings? <span class="r"><a href="#biossettings">#biossettings</a></span></h2>
 				<p>
 					Libreboot actually uses the <a href="http://www.coreboot.org/GRUB2">GRUB payload</a>.
 					More information about payloads can be found at <a href="http://www.coreboot.org/Payloads">coreboot.org/Payloads</a>.
@@ -507,7 +507,7 @@
 				<p>
 					<a href="#pagetop">Back to top of page</a>
 				</p>
-			<h2 id="bootloader">Do I need to install a bootloader when installing GNU/Linux? <span class="ref">(<a href="#bootloader">#bootloader</a>)</span></h2>
+			<h2 id="bootloader">Do I need to install a bootloader when installing GNU/Linux? <span class="r"><a href="#bootloader">#bootloader</a></span></h2>
 				<p>
 					Libreboot integrates the GRUB bootloader already, as a <i><a href="http://www.coreboot.org/Payloads">payload</a></i>. This means
 					that the GRUB bootloader is actually <i>flashed</i>, as part of the boot firmware (libreboot). This means that you do
@@ -522,7 +522,7 @@
 				<p>
 					<a href="#pagetop">Back to top of page</a>
 				</p>
-			<h2 id="reinstallos">Do I need to re-flash when I re-install GNU/Linux? <span class="ref">(<a href="#reinstallos">#reinstallos</a>)</span></h2>
+			<h2 id="reinstallos">Do I need to re-flash when I re-install GNU/Linux? <span class="r"><a href="#reinstallos">#reinstallos</a></span></h2>
 				<p>
 					Not anymore. Recent versions of libreboot (using the GRUB payload) will automatically
 					switch to a GRUB configuration on the HDD or SSD, if it exists. You can also load a different
@@ -538,7 +538,7 @@
 
 		<h1>Freedom questions</h1>
 
-			<h2 id="otherfirmware">What other firmware exists outside of libreboot? <span class="ref">(<a href="#otherfirmware">#otherfirmware</a>)</span></h2>
+			<h2 id="otherfirmware">What other firmware exists outside of libreboot? <span class="r"><a href="#otherfirmware">#otherfirmware</a></span></h2>
 
 				<p>
 					The main freedom issue on any system, is the boot firmware (usually referred to as a BIOS or UEFI). Libreboot replaces the boot firmware
@@ -554,12 +554,12 @@
 					Dealing with these problems will most likely be handled by a separate project.
 				</p>
 
-				<h3 id="firmware-ec">EC (embedded controller) firmware <span class="ref">(<a href="#firmware-ec">#firmware-ec</a>)</span></h3>
+				<h3 id="firmware-ec">EC (embedded controller) firmware <span class="r"><a href="#firmware-ec">#firmware-ec</a></span></h3>
 					<p>
 						Most (all?) laptops have this. The EC (embedded controller) is a small, separate processor that basically processes inputs/outputs
 						that are specific to laptops. For example:
 					</p>
-						<ul class="cascade">
+						<ul class="c">
 							<li>
 								When you flick the radio on/off switch, the EC will enable/disable the wireless devices (wifi, bluetooth, etc) and enable/disable
 								an LED that indicates whether it's turned on or not
@@ -591,7 +591,7 @@
 						<a href="#pagetop">Back to top of page</a>
 					</p>
 
-				<h3 id="firmware-hddssd">HDD/SSD firmware <span class="ref">(<a href="#firmware-hddssd">#firmware-hddssd</a>)</span></h3>
+				<h3 id="firmware-hddssd">HDD/SSD firmware <span class="r"><a href="#firmware-hddssd">#firmware-hddssd</a></span></h3>
 					<p>
 						HDDs and SSDs have firmware in them, intended to handle the internal workings of the device while exposing a simple,
 						standard interface (such as AHCI/SATA) that the OS software can use, generically. This firmware is transparent to the user
@@ -662,7 +662,7 @@
 					<p>
 						Other links:
 					</p>
-						<ul class="cascade">
+						<ul class="c">
 							<li><a href="http://motherboard.vice.com/read/the-nsas-undetectable-hard-drive-hack-was-first-demonstrated-a-year-ago">http://motherboard.vice.com/read/the-nsas-undetectable-hard-drive-hack-was-first-demonstrated-a-year-ago</a></li>
 						</ul>
 					<p>
@@ -670,7 +670,7 @@
 						online, that allow you to connect SATA HDDs via USB. Libreboot documents how to install several GNU/Linux distributions
 						with full disk encryption. You can adapt these for use with USB drives:
 					</p>
-						<ul class="cascade">
+						<ul class="c">
 							<li><a href="../docs/gnulinux/encrypted_trisquel.html">Full disk encryption with Trisquel GNU/Linux</a></li>
 							<li><a href="../docs/gnulinux/encrypted_parabola.html">Full disk encryption with Parabola GNU/Linux</a></li>
 						</ul>
@@ -685,7 +685,7 @@
 						<a href="#pagetop">Back to top of page</a>
 					</p>
 
-				<h3 id="firmware-nic">NIC (ethernet controller) <span class="ref">(<a href="#firmware-nic">#firmware-nic</a>)</span></h3>
+				<h3 id="firmware-nic">NIC (ethernet controller) <span class="r"><a href="#firmware-nic">#firmware-nic</a></span></h3>
 					<p>
 						Ethernet NICs will typically run firmware inside, which is responsible for initializing the device internally.
 						Theoretically, it could be configured to drop packets, or even modify them.
@@ -698,7 +698,7 @@
 						<a href="#pagetop">Back to top of page</a>
 					</p>
 
-				<h3 id="firmware-cpu">CPU microcode <span class="ref">(<a href="#firmware-cpu">#firmware-cpu</a>)</span></h3>
+				<h3 id="firmware-cpu">CPU microcode <span class="r"><a href="#firmware-cpu">#firmware-cpu</a></span></h3>
 					<p>
 						Implements an instruction set. See <a href="#microcode">#microcode</a> for a brief description.
 						Here we mean microcode built in to the CPU. We are not talking about the updates supplied by the boot firmware
@@ -718,7 +718,7 @@
 						<a href="#pagetop">Back to top of page</a>
 					</p>
 
-				<h3 id="firmware-sound">Sound card <span class="ref">(<a href="#firmware-sound">#firmware-sound</a>)</h3>
+				<h3 id="firmware-sound">Sound card <span class="r"><a href="#firmware-sound">#firmware-sound</a>)</h3>
 					<p>
 						Sound hardware (integrated or discrete) typically has firmware on it (DSP) for processing input/output.
 						Again, a USB DAC is a good workaround.
@@ -727,7 +727,7 @@
 						<a href="#pagetop">Back to top of page</a>
 					</p>
 
-				<h3 id="firmware-webcam">Web cam <span class="ref">(<a href="#firmware-webcam">#firmware-webcam</a></h3>
+				<h3 id="firmware-webcam">Web cam <span class="r"><a href="#firmware-webcam">#firmware-webcam</a></h3>
 					<p>
 						Webcams have firmware integrated into them that process the image input into the camera; adjusting focus,
 						white balancing and so on. Can use USB webcam hardware, to work around potential DMA issues; integrated webcams
@@ -737,7 +737,7 @@
 						<a href="#pagetop">Back to top of page</a>
 					</p>
 
-				<h3 id="firmware-usbhost">USB host controller <span class="ref">(<a href="#firmware-usbhost">#firmware-usbhost</a>)</span></h3>
+				<h3 id="firmware-usbhost">USB host controller <span class="r"><a href="#firmware-usbhost">#firmware-usbhost</a></span></h3>
 					<p>
 						Doesn't really apply to current libreboot systems (none of them have USB 3.0 at the moment), but
 						USB 3.0 host controllers typically rely on firmware to implement the XHCI specification. Some newer
@@ -753,7 +753,7 @@
 					<p>
 						<a href="#pagetop">Back to top of page</a>
 					</p>
-				<h3 id="firmware-wwan">WWAN firmware <span class="ref">(<a href="#firmware-wwan">#firmware-wwan</a>)</span></h3>
+				<h3 id="firmware-wwan">WWAN firmware <span class="r"><a href="#firmware-wwan">#firmware-wwan</a></span></h3>
 					<p>
 						Some laptops might have a simcard reader in them, with a card for handling WWAN, connecting to a 3g/4g (e.g. GSM) network.
 						This is the same technology used in mobile phones, for remote network access (e.g. internet).
@@ -786,7 +786,7 @@
 
 	<div>
 		<h1>Operating Systems</h1>
-			<h2 id="gnulinux">Can I use GNU/Linux? <span class="ref">(<a href="#gnulinux">#gnulinux</a>)</span></h2>
+			<h2 id="gnulinux">Can I use GNU/Linux? <span class="r"><a href="#gnulinux">#gnulinux</a></span></h2>
 				<p>
 					Absolutely! GNU/Linux is well-tested in libreboot, and highly recommended.
 					See <a href="../docs/gnulinux/grub_boot_installer.html">installing GNU/Linux</a> and <a href="../docs/gnulinux/grub_cbfs.html">booting GNU/Linux</a>.
@@ -803,7 +803,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="gnuhurd">Can I use GNU/Hurd? <span class="ref">(<a href="#gnuhurd">#gnuhurd</a>)</span></h2>
+			<h2 id="gnuhurd">Can I use GNU/Hurd? <span class="r"><a href="#gnuhurd">#gnuhurd</a></span></h2>
 				<p>
 					Unknown. Probably not. Feel free to try it, and report your findings.
 				</p>
@@ -819,7 +819,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="bsd">Can I use BSD? <span class="ref">(<a href="#bsd">#bsd</a>)</span></h2>
+			<h2 id="bsd">Can I use BSD? <span class="r"><a href="#bsd">#bsd</a></span></h2>
 				<p>
 					Potentially. It may be possible to boot most BSD systems if you use
 					the <a href="http://coreboot.org/SeaBIOS">SeaBIOS</a> payload.
@@ -839,7 +839,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="windows">Can I use Windows? <span class="ref">(<a href="#windows">#windows</a>)</span></h2>
+			<h2 id="windows">Can I use Windows? <span class="r"><a href="#windows">#windows</a></span></h2>
 				<p>
 					Windows is incompatible with libreboot, and will probably remain so. <a href="https://gnu.org/philosophy/malware-microsoft.html">Never use Windows</a>.
 				</p>
@@ -847,7 +847,7 @@
 					<a href="#pagetop">Back to top of page</a>
 				</p>
 
-			<h2 id="otheros">Are other operating systems compatible? <span class="ref">(<a href="#otheros">#otheros</a>)</span></h2>
+			<h2 id="otheros">Are other operating systems compatible? <span class="r"><a href="#otheros">#otheros</a></span></h2>
 				<p>
 					Unknown. Probably not.
 				</p>
--
cgit v0.9.1