Merge branch 'web/code-blocks' of vimuser/libreboot into master

15 files changed, 104 insertions, 71 deletions

diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md
index 408972e2..89f7ec67 100644
--- a/docs/install/bbb_setup.md
+++ b/docs/install/bbb_setup.md
@@ -46,6 +46,7 @@ Shopping list (pictures of this hardware is shown later):
     'Purchase'). We recommend this product because we know that it
     works well for our purposes and doesn't require any non-free
     software.
+
 -   Electrical/insulative tape: cover the entire bottom surface of the
     BBB (the part that rests on a surface). This is important, when
     placing the BBB on top of a board so that nothing shorts. Most
@@ -77,7 +78,7 @@ Shopping list (pictures of this hardware is shown later):
     powering with the USB cable, or if you want to use [EHCI
     debug](../misc/bbb_ehci.html)**.
 -   **Pin header / jumper cables** (2.54mm / 0.1" headers): you should
-    get male\--male, male\--female and female\--female cables in 10cm
+    get male--male, male--female and female--female cables in 10cm
     size. Just get a load of them. Other possible names for these
     cables/wires/leads are as follows:
     -   flying leads
@@ -97,7 +98,7 @@ Shopping list (pictures of this hardware is shown later):
 -   **FTDI TTL cable or debug board**: used for accessing the serial
     console on the BBB. [This
     page](http://elinux.org/Beagleboard:BeagleBone_Black_Serial)
-    contains a list. **OPTIONAL\-\--only needed for serial console on
+    contains a list. **OPTIONAL\---only needed for serial console on
     the BBB, if not using SSH via ethernet cable.**
 
 [Back to top of page.](#pagetop)
@@ -155,15 +156,15 @@ Alternatives to SSH (in case SSH fails)
 ---------------------------------------
 
 You can also use a serial FTDI debug board with GNU Screen, to access
-the serial console.\
-\# **screen /dev/ttyUSB0 115200**\
+the serial console.
+    # screen /dev/ttyUSB0 115200
 Here are some example photos:\
 ![](images/x200/ftdi.jpg) ![](images/x200/ftdi_port.jpg)\
 
 You can also connect the USB cable from the BBB to another computer and
 a new network interface will appear, with its own IP address. This is
-directly accessible from SSH, or screen:\
-\# **screen /dev/ttyACM0 115200**
+directly accessible from SSH, or screen:
+    # screen /dev/ttyACM0 115200
 
 You can also access the uboot console, using the serial method instead
 of SSH.
@@ -208,15 +209,17 @@ contents of this file with:
 
 Run **apt-get update** and **apt-get upgrade** then reboot the BBB,
 before continuing.
-Check that the firmware exists:\
-\# **ls /lib/firmware/BB-SPI0-01-00A0.\***\
+Check that the firmware exists:
+
+    # ls /lib/firmware/BB-SPI0-01-00A0.\*
 Output:
 
     /lib/firmware/BB-SPI0-01-00A0.dtbo
 
-Then:\
-\# **echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots**\
-\# **cat /sys/devices/bone\_capemgr.\*/slots**\
+Then:
+
+    # echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots
+    # cat /sys/devices/bone\_capemgr.\*/slots
 Output:
 
      0: 54:PF--- 
@@ -227,8 +230,9 @@ Output:
      5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
      7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01
 
-Verify that the spidev device now exists:\
-\# **ls -al /dev/spid\***\
+Verify that the spidev device now exists:
+
+    # ls -al /dev/spid\*
 Output:
 
     crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0
@@ -250,8 +254,9 @@ libreboot\_src, and put the ARM binary for it on your BBB.
 Finally, get the ROM image that you would like to flash and put that on
 your BBB.
 
-Now test flashrom:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+Now test flashrom:
+
+    # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 Output:
 
     Calibrating delay loop... OK.
diff --git a/docs/install/c201.md b/docs/install/c201.md
index 62812986..a811404d 100644
--- a/docs/install/c201.md
+++ b/docs/install/c201.md
@@ -37,6 +37,7 @@ root shell.
         parameters](#configuring_verified_boot_parameters)
     -   [Removing the write protect
         screw](#removing_write_protect_screw)
+
 -   [Installing Libreboot to the SPI flash]()
     -   [Installing Libreboot internally, from the
         device](#installing_libreboot_internally)
@@ -145,21 +146,23 @@ transferred to the device.
 
 The following operations have to be executed with root privileges on the
 device (e.g. using the *root* account). In addition, the
-**cros-flash-replace** script has to be made executable:\
-\# **chmod a+x cros-flash-replace**\
+**cros-flash-replace** script has to be made executable:
+    # chmod a+x cros-flash-replace
 
-The SPI flash has to be read first:\
-\# **flashrom -p host -r flash.img**\
+The SPI flash has to be read first:
+    # flashrom -p host -r flash.img\
 **Note: it might be a good idea to copy the produced flash.img file at
 this point and store it outside of the device for backup purposes.**
 
-Then, the **cros-flash-replace** script has to be executed as such:\
-\# **./cros-flash-replace flash.img coreboot ro-frid**\
+Then, the **cros-flash-replace** script has to be executed as such:
+
+    # ./cros-flash-replace flash.img coreboot ro-frid
 If any error is shown, it is definitely a bad idea to go further than
 this point.
 
-The resulting flash image can then be flashed back:\
-\# **flashrom -p host -w flash.img**\
+The resulting flash image can then be flashed back:
+
+    # flashrom -p host -w flash.img
 
 You should also see within the output the following:\
 **"Verifying flash\... VERIFIED."**
@@ -192,22 +195,26 @@ transferred to the host.
 
 The following operations have to be executed with root privileges on the
 host (e.g. using the *root* account). In addition, the
-**cros-flash-replace** script has to be made executable:\
-\# **chmod a+x cros-flash-replace**\
+**cros-flash-replace** script has to be made executable:
+
+    # chmod a+x cros-flash-replace
 
-The SPI flash has to be read first (using the right spi programmer):\
-\# **flashrom -p *programmer* -r flash.img**\
+The SPI flash has to be read first (using the right spi programmer):
+
+    # flashrom -p *programmer* -r flash.img
 **Note: it might be a good idea to copy the produced flash.img file at
 this point and store it outside of the device for backup purposes.**
 
-Then, the **cros-flash-replace** script has to be executed as such:\
-\# **./cros-flash-replace flash.img coreboot ro-frid**\
+Then, the **cros-flash-replace** script has to be executed as such:
+
+    # ./cros-flash-replace flash.img coreboot ro-frid
 If any error is shown, it is definitely a bad idea to go further than
 this point.
 
 The resulting flash image can then be flashed back (using the right spi
-programmer):\
-\# **flashrom -p *programmer* -w flash.img**\
+programmer):
+
+    # flashrom -p *programmer* -w flash.img
 
 You should also see within the output the following:\
 **"Verifying flash\... VERIFIED."**
diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md
index 39604c89..3a34bdbe 100644
--- a/docs/install/d510mo.md
+++ b/docs/install/d510mo.md
@@ -9,8 +9,9 @@ motherboard while they still have the original BIOS present.
 Flash chip size {#flashchips}
 ===============
 
-Use this to find out:\
-\# **flashrom -p internal -V**
+Use this to find out:
+    # flashrom -p internal -V
+
 
 [Back to top of page.](#pagetop)
 
diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md
index 75ec3dbd..ba6a9a30 100644
--- a/docs/install/ga-g41m-es2l.md
+++ b/docs/install/ga-g41m-es2l.md
@@ -9,8 +9,9 @@ motherboard while they still have the original BIOS present.
 Flash chip size {#flashchips}
 ===============
 
-Use this to find out:\
-\# **flashrom -p internal -V**
+Use this to find out:
+    # flashrom -p internal -V
+
 
 [Back to top of page.](#pagetop)
 
diff --git a/docs/install/index.md b/docs/install/index.md
index 25a3ad96..f8ee0e6a 100644
--- a/docs/install/index.md
+++ b/docs/install/index.md
@@ -30,6 +30,7 @@ Setting up programmers, for external flashing via hardware method
 
 -   [How to program an SPI flash chip with the BeagleBone
     Black](bbb_setup.html)
+
 -   [How to program an SPI flash chip with the Raspberry
     Pi](rpi_setup.html)
 
@@ -251,8 +252,8 @@ ROM image, and it should work.**
 Flash chip size
 ---------------
 
-Use this to find out:\
-\# **flashrom -p internal -V**
+Use this to find out:
+    # flashrom -p internal -V
 
 All good?
 ---------
@@ -271,15 +272,16 @@ appropriate executable. It is also possible for you to build these
 executables from the libreboot source code archives.
 
 
-How to update the flash chip contents:\
-\$ **sudo ./flash update [yourrom.rom](#rom)**
+How to update the flash chip contents:
+    $ sudo ./flash update [yourrom.rom](#rom)
 
 
 
 Ocassionally, coreboot changes the name of a given board. If flashrom
 complains about a board mismatch, but you are sure that you chose the
-correct ROM image, then run this alternative command:\
-\$ **sudo ./flash forceupdate [yourrom.rom](#rom)**
+correct ROM image, then run this alternative command:
+
+    $ sudo ./flash forceupdate [yourrom.rom](#rom)
 
 
 
@@ -318,8 +320,9 @@ the flashing script. do this: *rm -f patch && wget -O flash
 https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash
 && chmod +x flash***
 
-The first half of the procedure is as follows:\
-\$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).**
+The first half of the procedure is as follows:
+
+    $ sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).
 
 
 
@@ -342,8 +345,9 @@ and then boot; libreboot is running, but there is a 2nd procedure
 
 
 
-When you have booted up again, you must also do this:\
-\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)**
+When you have booted up again, you must also do this:
+
+    $ sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)
 
 If flashing fails at this stage, try the following:\
 \$ **sudo ./flashrom/i686/flashrom -p
@@ -391,8 +395,9 @@ Look at the [list of ROM images](#rom) to see which image is compatible
 with your device.
 
 
-Use this flashing script, to install libreboot:\
-\$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)**
+Use this flashing script, to install libreboot:
+
+    $ sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)
 
 
 
diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md
index 7789c1c8..0e78b274 100644
--- a/docs/install/kcma-d8.md
+++ b/docs/install/kcma-d8.md
@@ -17,6 +17,7 @@ TODO: show photos here, and other info.
 
 -   [kcma-d8 boards (and full systems) with libreboot
     preinstalled](#preinstall)
+
 -   [External programmer](#programmer)
 
 
diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md
index f9751f14..ed470a15 100644
--- a/docs/install/kgpe-d16.md
+++ b/docs/install/kgpe-d16.md
@@ -17,6 +17,7 @@ TODO: show photos here, and other info.
 
 -   [KGPE-D16 boards (and full systems) with libreboot
     preinstalled](#preinstall)
+
 -   [External programmer](#programmer)
 
 
diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md
index 00c8e3d4..40e49415 100644
--- a/docs/install/r400_external.md
+++ b/docs/install/r400_external.md
@@ -70,8 +70,9 @@ See [\#paste](#paste).
 Flash chip size {#flashchips}
 ===============
 
-Use this to find out:\
-\# **flashrom -p internal -V**\
+Use this to find out:
+    # flashrom -p internal -V
+
 
 [Back to top of page.](#pagetop)
 
@@ -228,8 +229,8 @@ source code which can be built.
 Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
-Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+Test that flashrom works:
+    # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512\
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -252,8 +253,9 @@ factory2.rom**\
 Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
-Now compare the 3 images:\
-\# **sha512sum factory\*.rom**\
+Now compare the 3 images:
+
+    # sha512sum factory\*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md
index 01cab733..9240038c 100644
--- a/docs/install/rpi_setup.md
+++ b/docs/install/rpi_setup.md
@@ -43,6 +43,7 @@ Guide](http://libreboot.org/docs/install/t60_unbrick.html).
 
 -   On the X60, the BIOS chip is on the bottom of the motherboard, under
     a layer of protective black tape.
+
 -   On the T60, the BIOS chip is just under the palmrest, but blocked by
     a magnesium frame (which you will have to remove).
 
diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md
index 029acf0f..4ddb6793 100644
--- a/docs/install/t400_external.md
+++ b/docs/install/t400_external.md
@@ -75,8 +75,9 @@ See [\#paste](#paste).
 Flash chip size {#flashchips}
 ===============
 
-Use this to find out:\
-\# **flashrom -p internal -V**
+Use this to find out:
+    # flashrom -p internal -V
+
 
 [Back to top of page.](#pagetop)
 
@@ -234,8 +235,8 @@ source code which can be built.
 Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
-Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+Test that flashrom works:
+    # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -258,8 +259,9 @@ factory2.rom**\
 Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
-Now compare the 3 images:\
-\# **sha512sum factory\*.rom**\
+Now compare the 3 images:
+
+    # sha512sum factory\*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md
index 5b07e6eb..2c350081 100644
--- a/docs/install/t500_external.md
+++ b/docs/install/t500_external.md
@@ -65,8 +65,9 @@ See [\#paste](#paste).
 Flash chip size {#flashchips}
 ===============
 
-Use this to find out:\
-\# **flashrom -p internal -V**
+Use this to find out:
+    # flashrom -p internal -V
+
 
 [Back to top of page.](#pagetop)
 
@@ -239,8 +240,8 @@ source code which can be built.
 Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
-Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+Test that flashrom works:
+    # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -263,8 +264,9 @@ factory2.rom**\
 Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
-Now compare the 3 images:\
-\# **sha512sum factory\*.rom**\
+Now compare the 3 images:
+
+    # sha512sum factory\*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md
index fc7a557f..309385b4 100644
--- a/docs/install/t60_unbrick.md
+++ b/docs/install/t60_unbrick.md
@@ -17,6 +17,7 @@ Table of Contents
 
 
 
+
 Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md
index a09e0374..78048867 100644
--- a/docs/install/x200_external.md
+++ b/docs/install/x200_external.md
@@ -33,8 +33,9 @@ Check the [suppliers](../../suppliers) page for more information.
 Flash chip size {#flashchips}
 ===============
 
-Use this to find out:\
-\# **flashrom -p internal -V**
+Use this to find out:
+    # flashrom -p internal -V
+
 
 The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of
 the motherboard (this requires removal of the motherboard). **Not all
@@ -168,8 +169,8 @@ source code which can be built.
 Log in as root on your BBB, using the instructions in
 [bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access).
 
-Test that flashrom works:\
-\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\
+Test that flashrom works:
+    # ./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512
 In this case, the output was:
 
     flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l)
@@ -192,8 +193,9 @@ factory2.rom**\
 Note: the **-c** option is not required in libreboot's patched
 flashrom, because the redundant flash chip definitions in *flashchips.c*
 have been removed.\
-Now compare the 3 images:\
-\# **sha512sum factory\*.rom**\
+Now compare the 3 images:
+
+    # sha512sum factory\*.rom
 If the hashes match, then just copy one of them (the factory.rom) to a
 safe place (on a drive connected to another system, not the BBB). This
 is useful for reverse engineering work, if there is a desirable
diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md
index 33a4fef3..b6710a99 100644
--- a/docs/install/x60_unbrick.md
+++ b/docs/install/x60_unbrick.md
@@ -17,6 +17,7 @@ Table of Contents
 
 
 
+
 Brick type 1: bucts not reset. {#bucts_brick}
 ==============================
 
diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md
index cc62ecaf..0a1801b1 100644
--- a/docs/install/x60tablet_unbrick.md
+++ b/docs/install/x60tablet_unbrick.md
@@ -17,6 +17,7 @@ Table of Contents
 
 
 
+
 Brick type 1: bucts not reset. {#bucts_brick}
 ==============================