diff options
Diffstat (limited to 'docs/misc')
| -rw-r--r-- | docs/misc/bbb_ehci.md | 36 | ||||
| -rw-r--r-- | docs/misc/index.md | 22 | ||||
| -rw-r--r-- | docs/misc/patch.md | 26 |
3 files changed, 42 insertions, 42 deletions
diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md index 3a48837f..5ff5f820 100644 --- a/docs/misc/bbb_ehci.md +++ b/docs/misc/bbb_ehci.md @@ -128,19 +128,19 @@ Make sure that you have cross compiling environment for arm-linux-gnueabihf setup on your *host*. - On BBB: uname -r - this will give you version number like - 3.8.13-bone70 (I will refer to this as: $mav.$miv-$lv: where + 3.8.13-bone70 (I will refer to this as: \$mav.\$miv-\$lv: where mav=3.8, miv=13, lv=bone70 - Get the BBB kernel ready on your host for cross-compiling: <!-- --> - $ cd $work_dir - $ git clone https://github.com/beagleboard/kernel.git - $ cd kernel - $ git checkout $mav (see above) - $ ./patch.sh - $ wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin - $ cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig + \$ cd \$work_dir + \$ git clone https://github.com/beagleboard/kernel.git + \$ cd kernel + \$ git checkout \$mav (see above) + \$ ./patch.sh + \$ wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin + \$ cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig - Download the patch from [here](http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz) @@ -150,7 +150,7 @@ arm-linux-gnueabihf setup on your *host*. the two different version of the kernel (3.8 and 3.10). I will use 3.8. (If using kernel 3.12 patch\_1 is not needed) - cd kernel (note that this is one more level: you should be in - $work\_dir/kernel/kernel) + \$work\_dir/kernel/kernel) - Apply the patches: <!-- --> @@ -166,12 +166,12 @@ arm-linux-gnueabihf setup on your *host*. see [scripts](http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/). - Get your current BBB kernel config (from: /boot/config-<ver>) - and copy it to your host as $work\_dir/kernel/kernel/.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 + - 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 - it to CONFIG\_LOCALVERSION="-$lv", so it will look something + 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 @@ -180,12 +180,12 @@ arm-linux-gnueabihf setup on your *host*. <!-- --> - $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 (is it possoble to build only the gadget modules) - $ mkdir ../tmp && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=../tmp modules_install + \$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 (is it possoble to build only the gadget modules) + \$ mkdir ../tmp && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=../tmp modules_install - on BBB, backup /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget (i.e. mv /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget - $HOME) + \$HOME) - copy the freshly compiled usb/gadget dir to /lib/modules/3.8.13-bone70/kernel/drivers/usb - restart BBB @@ -200,14 +200,14 @@ push debug messages to the EHCI debug port. If you've downloaded the binary distribution, you can check if it is properly configured in the following way: -- Go to the libreboot dist root directory cd $libreboot\_bin -- Locate the rom image for your target (I will call it: $img\_path) +- Go to the libreboot dist root directory cd \$libreboot\_bin +- Locate the rom image for your target (I will call it: \$img\_path) - Running the following command will extract the config in a file ./my\_config: <!-- --> - ./cbfstool/i686/cbfstool $img_path extract -n config -f ./my_config + ./cbfstool/i686/cbfstool \$img_path extract -n config -f ./my_config - Make sure that the following params in the config are set as following: diff --git a/docs/misc/index.md b/docs/misc/index.md index 6f217d80..096842df 100644 --- a/docs/misc/index.md +++ b/docs/misc/index.md @@ -24,7 +24,7 @@ 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 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 @@ -50,7 +50,7 @@ GRUB. These consume power. Stop using them! Be root - $ su - + \$ su - Installed powertop: @@ -99,7 +99,7 @@ USB Serial adapter. On the 2nd system, you can try this (using GNU Screen): - $ sudo screen /dev/ttyUSB0 115200 + \$ sudo screen /dev/ttyUSB0 115200 How to quit GNU Screen: Ctrl+A then release and press K, and then press Y. @@ -215,13 +215,13 @@ behaviour. Disable or enable beeps when removing/adding the charger: - $ sudo ./nvramtool -w power\_management\_beeps=Enable -$ **sudo ./nvramtool -w power\_management\_beeps=Disable** + \$ 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 -$ **sudo ./nvramtool -w low\_battery\_beep=Disable** + \$ sudo ./nvramtool -w low\_battery\_beep=Enable +\$ **sudo ./nvramtool -w low\_battery\_beep=Disable** A reboot is required, for these changes to take effect. @@ -234,11 +234,11 @@ 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 + \$ sudo modprobe i2c-dev +\$ **sudo i2cdump -y 5 0x50** (you might have to change the value for -y) - $ sudo rmmod i2c-dev + \$ 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 @@ -266,7 +266,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). diff --git a/docs/misc/patch.md b/docs/misc/patch.md index 318c7428..6164986c 100644 --- a/docs/misc/patch.md +++ b/docs/misc/patch.md @@ -9,12 +9,12 @@ 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 @@ -24,7 +24,7 @@ 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 @@ -34,7 +34,7 @@ file names. For example: 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 @@ -42,7 +42,7 @@ 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) @@ -51,15 +51,15 @@ 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 + \$ 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) @@ -72,15 +72,15 @@ 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 + \$ git log Alternatively (better yet), commit your changes and then use: - $ git format-patch -N + \$ git format-patch -N Replace N with the number of commits that you want to show. [Back to top of page.](#pagetop) @@ -93,11 +93,11 @@ 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 + \$ git reset \--hard REVISIONNUMBER 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 |