From 60926e9fc770fc1f310306447220cb3740382b00 Mon Sep 17 00:00:00 2001 From: Alyssa Rosenzweig Date: Fri, 17 Mar 2017 22:44:31 -0700 Subject: Let markdown handle <> gracefully --- docs/misc/bbb_ehci.md | 20 ++++++++++---------- docs/misc/index.md | 8 ++++---- docs/misc/patch.md | 18 +++++++++--------- 3 files changed, 23 insertions(+), 23 deletions(-) (limited to 'docs/misc') diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md index 9e9314ce..0246a382 100644 --- a/docs/misc/bbb_ehci.md +++ b/docs/misc/bbb_ehci.md @@ -168,17 +168,17 @@ arm-linux-gnueabihf setup on your *host*. [fsfla website](http://www.fsfla.org/ikiwiki/selibre/linux-libre/) - see [scripts](http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/). -- Get your current BBB kernel config (from: /boot/config-<ver>) +- Get your current BBB kernel config (from: /boot/config-) and copy it to your host as \$work\_dir/kernel/kernel/.config - Set proper version number: - On your host, edit \$work\_dir/kernel/kernel/.config (the one you've just copied from BBB), find the line - CONFIG\_LOCALVERSION="<something or empty>" and change + CONFIG\_LOCALVERSION="" and change it to CONFIG\_LOCALVERSION="-\$lv", so it will look something like: CONFIG\_LOCALVERSION="-bone70" - Also, make sure that: CONFIG\_USB\_G\_DBGP=m (If not, make - menuconfig, and set @Device Drivers-> USB Support -> USB - Gadget Support -> EHCI Debug Device Gadget=m + menuconfig, and set @Device Drivers-> USB Support -> USB + Gadget Support -> EHCI Debug Device Gadget=m - Build the module: @@ -192,7 +192,7 @@ arm-linux-gnueabihf setup on your *host*. - copy the freshly compiled usb/gadget dir to /lib/modules/3.8.13-bone70/kernel/drivers/usb - restart BBB -- Remove all g\_\* modules (rmmod g\_<>) +- Remove all g\_\* modules (rmmod g\_<>) - modprobpe g\_dbgp ### Configure libreboot with EHCI debug {#ConfigurelibrebootwithEHCIdebug} @@ -238,7 +238,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 ) @@ -302,14 +302,14 @@ rmmod g\_\* and modprobe g\_dbgp You have to know how to compile kernel for your target. 1. Check if early debugging is already enabled: grep - CONFIG\_EARLY\_PRINTK\_DBGP /boot/config-<ver> + CONFIG\_EARLY\_PRINTK\_DBGP /boot/config- 2. If enabled, you do not have to compile the kernel (skip this step). Otherwise, prepare kernel source for your distribution and select - (Kernel hacking -> Early printk via EHCI debug port). Compile and + (Kernel hacking -> Early printk via EHCI debug port). Compile and install the new kernel. 3. Edit your grub configuration and add following to the kenel parameters^[20](#___fn20)[21](#___fn21)^: earlyprintk=dbgp,keep. - Also, try: earlyprintk=dbgp<N>,keep where N is the debug port + Also, try: earlyprintk=dbgp,keep where N is the debug port id if the first does not work. ### References {#References} @@ -356,7 +356,7 @@ Interface](http://cs.usfca.edu/~cruse/cs698s10/) -Copyright © 2015 Alex David <opdecirkel@gmail.com>\ +Copyright © 2015 Alex David \ 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 diff --git a/docs/misc/index.md b/docs/misc/index.md index a24631a3..44503755 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -151,7 +151,7 @@ on intel gpu's is included in intel-gpu-tools. Install intel-gpu-tools: **sudo apt-get install intel-gpu-tools** You can set values: **sudo intel\_reg write 0x00061254 -<your\_value>** +<your\_value>** The value set has the following structure: bits \[31:16\] is PWM divider. PWM / PWM\_divider = frequency bits \[15:0\] is the duty cycle @@ -211,7 +211,7 @@ duty cycle. see on bit 16. The cause of this issue is that i945, in contrast with to GM45, is set to work in BLM Legacy Mode. This makes backlight more complicated since the duty cycle is derived from 3 instead of 2 registers using the following -formula: if(BPC\[7:0\] <> xFF) then BPCR\[15:0\] \* BPC\[7:0\] +formula: if(BPC\[7:0\] <> xFF) then BPCR\[15:0\] \* BPC\[7:0\] Else BPCR\[15:0\] BPC is LBB - PCI Backlight Control Register, described on on page 315. BPCR is BLC\_PWM\_CTL described in @@ -280,7 +280,7 @@ laptop. If power usage is a concern, then you should not use this. To disable c-states, do this in GNU+Linux:\ **for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable; do echo 1 -> \$i; done** +> \$i; done** You can reproduce this issue more easily by sending lots of traffic across subnets on the same interface (NIC). @@ -299,7 +299,7 @@ Put this script in /etc/init.d/ on debian-based systems. -Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ +Copyright © 2014, 2015, 2016 Leah Rowe \ 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 diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 073fdf9c..9f6125c5 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -12,11 +12,11 @@ Apply a patch ============= To apply a patch to a single file, do that in it's directory:\ -**\$ patch < foo.patch** +**\$ 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** +**\$ 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 @@ -25,7 +25,7 @@ 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** +**\$ 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 @@ -33,14 +33,14 @@ 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** +**\$ 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** +**\$ patch -p5 -R < baz.patch** [Back to top of page.](#pagetop) @@ -50,13 +50,13 @@ Create a patch with diff ======================== Diff can create a patch for a single file:\ -**\$ diff -u original.c new.c > original.patch** +**\$ diff -u original.c new.c > original.patch** For diff'ing a source tree:\ **\$ cp -R original new** Do whatever you want in new/ and then diff it:\ -**\$ diff -rupN original/ new/ > original.patch** +**\$ diff -rupN original/ new/ > original.patch** [Back to top of page.](#pagetop) @@ -70,7 +70,7 @@ 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** +**\$ git diff > patch.git** Note the git revision that you did this with:\ **\$ git log** @@ -103,7 +103,7 @@ aswell, instead of just applying the patch. -Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Copyright © 2014, 2015 Leah Rowe \ 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 -- cgit v1.2.3-70-g09d2