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

3 files changed, 74 insertions, 52 deletions

diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md
index db2d1969..51fd40df 100644
--- a/docs/misc/bbb_ehci.md
+++ b/docs/misc/bbb_ehci.md
@@ -9,6 +9,7 @@ EHCI debugging
 
 1.  [Find USB port on the target that supports EHCI
     debug](#FindUSBportonthetargetthatsupportsEHCIdebug)
+
 2.  [Initial setup of BBB to act as EHCI debug
     dongle](#InitialsetupofBBBtoactasEHCIdebugdongle)
 3.  [Patch BBB's `g_dbgp` module (optional, but highly
@@ -236,7 +237,7 @@ Then:\
 
     CONFIG_CONSOLE_USB=y (Console -> USB dongle console output)
 
-Also Debugging \-\--> Output verbose XYZ ) (**FIXME** somebody verify
+Also Debugging \---> Output verbose XYZ ) (**FIXME** somebody verify
 these):
 
     CONFIG_DEBUG_CBFS=y (Output verbose CBFS debug messages )
diff --git a/docs/misc/index.md b/docs/misc/index.md
index 05265091..dabe1e54 100644
--- a/docs/misc/index.md
+++ b/docs/misc/index.md
@@ -3,6 +3,7 @@
 
 -   [High Pitched Whining Noise on Idle (how to remove in Debian or
     Devuan)](#debian_powertop)
+
 -   [High Pitched Whining Noise on Idle (how to remove in
     Parabola)](#high_pitch_parabola)
 -   [X60/T60: Serial port - how to use (for dock owners)](#serial)
@@ -25,12 +26,12 @@ Start powertop automatically at boot time {#debian_powertop_autostart}
 -----------------------------------------
 
 Included with libreboot is a script called 'powertop.debian'. Run this
-as root and it will setup powertop to run with \--auto-tune at boot
+as root and it will setup powertop to run with --auto-tune at boot
 time. Load the file in your text editor to see how it does that.
 
-\$ **sudo ./resources/scripts/misc/powertop.debian**
+    $ sudo ./resources/scripts/misc/powertop.debian
 
-Might want to run with \--calibrate first
+Might want to run with --calibrate first
 
 If powertop doesn't work, another way (reduces battery life slightly)
 is to add *processor.max\_cstate=2* to the *linux* line in grub.cfg,
@@ -50,18 +51,20 @@ most people can't hear or doesn't bother most people).
 
 This is not perfect! The full solution is still not discovered but this
 is a step towards that. Also, in some instances you will need to run
-'sudo powertop \--auto-tune' again. This needs to be implemented
+'sudo powertop --auto-tune' again. This needs to be implemented
 properly in coreboot itself!
 
 On the X60 with coreboot or libreboot, there is a high pitched sound
 when idle. So far we have use processor.max\_cstate=2 or idle=halt in
 GRUB. These consume power. Stop using them!
 
-Be root\
-**\$ su -**
+Be root
+
+    $ su -
 
-Installed powertop:\
-**\# pacman -S powertop**
+Installed powertop:
+
+    # pacman -S powertop
 
 and added the following to /etc/systemd/system/powertop.service :
 
@@ -78,13 +81,14 @@ and added the following to /etc/systemd/system/powertop.service :
     [Install]
     WantedBy=multi-user.target
 
-Finally, as root do that:\
-**\# systemctl enable powertop**\
-**\# systemctl start powertop**
+Finally, as root do that:
+
+    # systemctl enable powertop
+    # systemctl start powertop
 
 The next time you boot the system, the buzz will be gone.
 
-Might want to run with \--calibrate first
+Might want to run with --calibrate first
 
 If powertop doesn't work, another way (reduces battery life slightly)
 is to add *processor.max\_cstate=2* to the *linux* line in grub.cfg,
@@ -107,8 +111,9 @@ included inside the ROM. Connect your null modem cable to the serial
 port on the dock and connect the other end to a 2nd system using your
 USB Serial adapter.
 
-On the 2nd system, you can try this (using GNU Screen):\
-**\$ sudo screen /dev/ttyUSB0 115200**
+On the 2nd system, you can try this (using GNU Screen):
+
+    $ sudo screen /dev/ttyUSB0 115200
 
 How to quit GNU Screen: Ctrl+A then release and press K, and then press
 Y.
@@ -227,13 +232,14 @@ battery goes to a critically low charge level, a beep occurs. Nvramtool
 is included in libreboot, and can be used to enable or disable this
 behaviour.
 
-Disable or enable beeps when removing/adding the charger:\
-\$ **sudo ./nvramtool -w power\_management\_beeps=Enable**\
-\$ **sudo ./nvramtool -w power\_management\_beeps=Disable**
+Disable or enable beeps when removing/adding the charger:
+    $ sudo ./nvramtool -w power\_management\_beeps=Enable
+    $ sudo ./nvramtool -w power\_management\_beeps=Disable
+
+Disable or enable beeps when battery is low:
+    $ sudo ./nvramtool -w low\_battery\_beep=Enable
 
-Disable or enable beeps when battery is low:\
-\$ **sudo ./nvramtool -w low\_battery\_beep=Enable**\
-\$ **sudo ./nvramtool -w low\_battery\_beep=Disable**
+    $ sudo ./nvramtool -w low\_battery\_beep=Disable
 
 A reboot is required, for these changes to take effect.
 
@@ -246,11 +252,13 @@ Get the panel name with **sudo get-edid | strings**\
 Or look in **/sys/class/drm/card0-LVDS-1/edid**
 
 Alternatively you can use i2cdump. In Debian and Devuan, this is in the
-package i2c-tools.\
-\$ **sudo modprobe i2c-dev**\
-\$ **sudo i2cdump -y 5 0x50** (you might have to change the value for
--y)\
-\$ **sudo rmmod i2c-dev**\
+package i2c-tools.
+
+    $ sudo modprobe i2c-dev
+    $ sudo i2cdump -y 5 0x50 (you might have to change the value for
+-y)
+
+    $ sudo rmmod i2c-dev
 You'll see the panel name in the output (from the EDID dump).
 
 If neither of these options work (or they are unavailable), physically
diff --git a/docs/misc/patch.md b/docs/misc/patch.md
index 8359ecd6..73d4979a 100644
--- a/docs/misc/patch.md
+++ b/docs/misc/patch.md
@@ -9,12 +9,15 @@ This is just a quick guide for reference, use 'man' to know more.
 Apply a patch
 =============
 
-To apply a patch to a single file, do that in it's directory:\
-**\$ patch < foo.patch**
+To apply a patch to a single file, do that in it's directory:
+
+    $ patch < foo.patch
+
 
 Assuming that the patch is distributed in unified format identifying the
-file the patch should be applied to, the above will work. Otherwise:\
-**\$ patch foo.txt < bar.patch**
+file the patch should be applied to, the above will work. Otherwise:
+
+    $ patch foo.txt < bar.patch
 
 You can apply a patch to an entire directory, but note the "p level".
 What this means is that inside patch files will be the files that you
@@ -22,23 +25,26 @@ intend to patch, identified by path names that might be different when
 the files ane located on your own computer instead of on the computer
 where the patch was created. 'p' level instructs the 'patch' utility
 to ignore parts of the path name to identify the files correctly.
-Usually a p level of 1 will work, so you would use:\
-**\$ patch -p1 < baz.patch**
+Usually a p level of 1 will work, so you would use:
+
+    $ patch -p1 < baz.patch
 
 Change to the top level directory before running this. If a patch level
 of 1 cannot identify the files to patch, then inspect the patch file for
 file names. For example:\
 **/home/user/do/not/panic/yet.c**
 
-and you are working in a directory that contains panic/yet.c, use:\
-**\$ patch -p5 < baz.patch**
+and you are working in a directory that contains panic/yet.c, use:
+
+    $ patch -p5 < baz.patch
 
 You usually count one up for each path separator (forward slash) removed
 from the beginning of the path, until you are left with a path that
 exists in the current working directory. The count is the p level.
 
-Removing a patch using the -R flag\
-**\$ patch -p5 -R < baz.patch**
+Removing a patch using the -R flag
+
+    $ patch -p5 -R < baz.patch
 
 [Back to top of page.](#pagetop)
 
@@ -47,14 +53,17 @@ Removing a patch using the -R flag\
 Create a patch with diff
 ========================
 
-Diff can create a patch for a single file:\
-**\$ diff -u original.c new.c > original.patch**
+Diff can create a patch for a single file:
+
+    $ diff -u original.c new.c > original.patch
 
-For diff'ing a source tree:\
-**\$ cp -R original new**
+For diff'ing a source tree:
 
-Do whatever you want in new/ and then diff it:\
-**\$ diff -rupN original/ new/ > original.patch**
+    $ cp -R original new
+
+Do whatever you want in new/ and then diff it:
+
+    $ diff -rupN original/ new/ > original.patch
 
 [Back to top of page.](#pagetop)
 
@@ -67,14 +76,16 @@ git is something special.
 
 Note: this won't show new files created.
 
-Just make whatever changes you want to a git clone and then:\
-**\$ git diff > patch.git**
+Just make whatever changes you want to a git clone and then:
+
+    $ git diff > patch.git
 
-Note the git revision that you did this with:\
-**\$ git log**
+Note the git revision that you did this with:
 
-Alternatively (better yet), commit your changes and then use:\
-\$ **git format-patch -N**\
+    $ git log
+
+Alternatively (better yet), commit your changes and then use:
+    $ git format-patch -N
 Replace N with the number of commits that you want to show.
 
 [Back to top of page.](#pagetop)
@@ -87,11 +98,13 @@ git apply
 it really is.
 
 Now to apply that patch in the future, just git clone it again and do
-with the git revision you found from above:\
-**\$ git reset \--hard REVISIONNUMBER**
+with the git revision you found from above:
+
+    $ git reset --hard REVISIONNUMBER
+
+Now put patch.git in the git clone directory and do:
 
-Now put patch.git in the git clone directory and do:\
-**\$ git apply patch.git**
+    $ git apply patch.git
 
 If you use a patch from git format-patch, then use **git am patch.git**
 instead of **git apply patch.git**. git-am will re-create the commits