libreboot

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README

commit dd3a800d82e0b9a4f1a785d61fd17fa202cb0e2c
parent 14ac959780ab3dc09559a17d4c12b7fd3705be6f
Author: Alyssa Rosenzweig <alyssa@rosenzweig.io>
Date:   Fri, 17 Mar 2017 23:50:52 -0700

I can escape good

Diffstat:
docs/bsd/freebsd.md | 16++++++++--------
docs/bsd/netbsd.md | 16++++++++--------
docs/bsd/openbsd.md | 16++++++++--------
docs/future/index.md | 2+-
docs/git/index.md | 28++++++++++++++--------------
docs/gnulinux/configuring_parabola.md | 2+-
docs/gnulinux/encrypted_parabola.md | 10+++++-----
docs/gnulinux/grub_boot_installer.md | 16++++++++--------
docs/gnulinux/grub_cbfs.md | 14+++++++-------
docs/grub/index.md | 8++++----
docs/hcl/gm45_remove_me.md | 6+++---
docs/hcl/index.md | 2+-
docs/hcl/t500.md | 2+-
docs/index.md | 2+-
docs/install/bbb_setup.md | 4++--
docs/misc/bbb_ehci.md | 22+++++++++++-----------
docs/misc/index.md | 12++++++------
docs/misc/patch.md | 26+++++++++++++-------------
docs/publish.sh | 2+-
19 files changed, 103 insertions(+), 103 deletions(-)

diff --git a/docs/bsd/freebsd.md b/docs/bsd/freebsd.md @@ -57,20 +57,20 @@ how to create the bootable FreeBSD USB drive: Connect the USB drive. Check dmesg: - \$ dmesg | tail + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3: - \$ disklabel sd3 + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ doas umount /dev/sd3i + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the FreeBSD installer to it with dd. For example: - \$ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync + $ doas dd if=freebsd.img of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -83,21 +83,21 @@ the bootable FreeBSD USB drive: Connect the USB drive. Check dmesg: - \$ dmesg + $ dmesg Check lsblk to confirm which drive it is: - \$ lsblk + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ sudo umount /dev/sdX* + $ sudo umount /dev/sdX* # umount /dev/sdX* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example: - \$ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync + $ sudo dd if=freebsd.img of=/dev/sdX bs=8M; sync # dd if=freebsd.img of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. diff --git a/docs/bsd/netbsd.md b/docs/bsd/netbsd.md @@ -53,20 +53,20 @@ to create the bootable NetBSD USB drive: Connect the USB drive. Check dmesg: - \$ dmesg | tail + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3: - \$ disklabel sd3 + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ doas umount /dev/sd3i + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the NetBSD installer to it with dd. For example: - \$ doas netbsd.iso of=/dev/rsdXc bs=1M; sync + $ doas netbsd.iso of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -79,21 +79,21 @@ the bootable NetBSD USB drive: Connect the USB drive. Check dmesg: - \$ dmesg + $ dmesg Check lsblk to confirm which drive it is: - \$ lsblk + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ sudo umount /dev/sdX* + $ sudo umount /dev/sdX* # umount /dev/sdX* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example: - \$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync + $ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync # dd if=netbsd.iso of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. diff --git a/docs/bsd/openbsd.md b/docs/bsd/openbsd.md @@ -35,20 +35,20 @@ how to create the bootable LibertyBSD/OpenBSD USB drive: Connect the USB drive. Check dmesg: - \$ dmesg | tail + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3: - \$ disklabel sd3 + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ doas umount /dev/sd3i + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the OpenBSD installer to it with dd. For example: - \$ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync + $ doas dd if=install60.fs of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. @@ -78,21 +78,21 @@ the bootable OpenBSD USB drive: Connect the USB drive. Check dmesg: - \$ dmesg + $ dmesg Check lsblk to confirm which drive it is: - \$ lsblk + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ sudo umount /dev/sdX* + $ sudo umount /dev/sdX* # umount /dev/sdX* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example: - \$ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync + $ sudo dd if=install60.fs of=/dev/sdX bs=8M; sync # dd if=install60.fs of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. diff --git a/docs/future/index.md b/docs/future/index.md @@ -335,7 +335,7 @@ of=runningvga.bin skip=12 count=1** Then do (and record the output): - \$ ./intelvbttool runningvga.bin > intelvbttool\_out + $ ./intelvbttool runningvga.bin > intelvbttool\_out Backup both files (runningvga.bin and intelvbttool\_out), renaming them to match the system and LCD panel used. diff --git a/docs/git/index.md b/docs/git/index.md @@ -28,12 +28,12 @@ statically compiled executables for the utilities are included.** For Debian Stretch (may also work on Debian Jessie), you can run the following command: - \$ sudo ./oldbuild dependencies debian + $ sudo ./oldbuild dependencies debian (this will also work in Devuan) For Parabola, you can run the following command: - \$ sudo ./oldbuild dependencies parabola + $ sudo ./oldbuild dependencies parabola or: # **./oldbuild dependencies parabola** @@ -57,18 +57,18 @@ Since libreboot makes extensive use of git, you need to configure git properly. If you have not yet configured git, then the minimum requirement is: - \$ git config \--global user.name "Your Name" - \$ git config \--global user.email your@emailaddress.com + $ git config \--global user.name "Your Name" + $ git config \--global user.email your@emailaddress.com This is what will also appear in git logs if you ever commit your own changes to a given repository. For more information, see <http://git-scm.com/doc>. Another nice config for you (optional, but recommended): - \$ git config \--global core.editor nano - \$ git config \--global color.status auto - \$ git config \--global color.branch auto - \$ git config \--global color.interactive auto + $ git config \--global core.editor nano + $ git config \--global color.status auto + $ git config \--global color.branch auto + $ git config \--global color.interactive auto \$ **git config \--global color.diff auto** After that, run the script: @@ -220,13 +220,13 @@ modulename*. To see the possible values for *modulename*, use: After that, build the ROM images (for all boards): - \$ ./oldbuild roms withgrub + $ ./oldbuild roms withgrub Alternatively, you can build for a specific board or set of boards. For example: - \$ ./oldbuild roms withgrub x60 - \$ ./oldbuild roms withgrub x200\_8mb - \$ ./oldbuild roms withgrub x60 x200\_8mb + $ ./oldbuild roms withgrub x60 + $ ./oldbuild roms withgrub x200\_8mb + $ ./oldbuild roms withgrub x60 x200\_8mb The list of board options can be found by looking at the directory names in **resources/libreboot/config/grub/**. @@ -311,7 +311,7 @@ libreboot\_util, for: If you are building binaries on a live system or chroot (for flashrom/bucts), you can use the following to statically link them: - \$ ./oldbuild module flashrom static + $ ./oldbuild module flashrom static \$ **./oldbuild module bucts static** The same conditions as above apply for ARM (except, building bucts on @@ -323,7 +323,7 @@ restrictions). The command that you used for generating the release archives will also run the following command: - \$ ./oldbuild release tobuild + $ ./oldbuild release tobuild The archive **tobuild.tar.xz** will have been created under **release/oldbuildsystem/**, containing bucts, flashrom and all other required resources for building them. diff --git a/docs/gnulinux/configuring_parabola.md b/docs/gnulinux/configuring_parabola.md @@ -638,7 +638,7 @@ start lxde without lxdm. Read Open LXterminal: - \$ cp /etc/skel/.xinitrc \~ + $ cp /etc/skel/.xinitrc \~ Open .xinitrc and add the following plus a line break at the bottom of the file. diff --git a/docs/gnulinux/encrypted_parabola.md b/docs/gnulinux/encrypted_parabola.md @@ -572,10 +572,10 @@ option at the end, with the name of your chosen chip is quotes. You can check if everything is in there (*grub.cfg* and *grubtest.cfg* would be really nice): - \$ ./cbfstool libreboot.rom print + $ ./cbfstool libreboot.rom print Extract grubtest.cfg: - \$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg + $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg And modify: \$ **vi grubtest.cfg** @@ -608,7 +608,7 @@ hardening your GRUB configuration, for security purposes. Save your changes in grubtest.cfg, then delete the unmodified config from the ROM image: - \$ ./cbfstool libreboot.rom remove -n grubtest.cfg + $ ./cbfstool libreboot.rom remove -n grubtest.cfg and insert the modified grubtest.cfg: \$ **./cbfstool libreboot.rom add -n grubtest.cfg -f grubtest.cfg -t @@ -656,10 +656,10 @@ grub.cfg** Delete the grub.cfg that remained inside the ROM: - \$ ./cbfstool libreboot.rom remove -n grub.cfg + $ ./cbfstool libreboot.rom remove -n grub.cfg Add the modified version that you just made: - \$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw + $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw Now you have a modified ROM. Once more, refer to <http://libreboot.org/docs/install/#flashrom>. Cd to the libreboot\_util diff --git a/docs/gnulinux/grub_boot_installer.md b/docs/gnulinux/grub_boot_installer.md @@ -26,21 +26,21 @@ to create the bootable GNU+Linux USB drive: Connect the USB drive. Check dmesg: - \$ dmesg + $ dmesg Check lsblk to confirm which drive it is: - \$ lsblk + $ lsblk Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ sudo umount /dev/sdX* + $ sudo umount /dev/sdX* # umount /dev/sdX* dmesg told you what device it is. Overwrite the drive, writing your distro ISO to it with dd. For example: - \$ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync + $ sudo dd if=gnulinux.iso of=/dev/sdX bs=8M; sync # dd if=gnulinux.iso of=/dev/sdX bs=8M; sync You should now be able to boot the installer from your USB drive. @@ -71,20 +71,20 @@ how to create the bootable GNU+Linux USB drive: Connect the USB drive. Check dmesg: - \$ dmesg | tail + $ dmesg | tail Check to confirm which drive it is, for example, if you think its sd3: - \$ disklabel sd3 + $ disklabel sd3 Check that it wasn't automatically mounted. If it was, unmount it. For example: - \$ doas umount /dev/sd3i + $ doas umount /dev/sd3i dmesg told you what device it is. Overwrite the drive, writing the OpenBSD installer to it with dd. For example: - \$ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync + $ doas dd if=gnulinux.iso of=/dev/rsdXc bs=1M; sync You should now be able to boot the installer from your USB drive. Continue reading, for information about how to do that. diff --git a/docs/gnulinux/grub_cbfs.md b/docs/gnulinux/grub_cbfs.md @@ -130,7 +130,7 @@ image file is named *libreboot.rom*, so please make sure to adapt. ROM images are included pre-compiled in libreboot. You can also dump your current firmware, using flashrom: - \$ sudo flashrom -p internal -r libreboot.rom + $ sudo flashrom -p internal -r libreboot.rom # flashrom -p internal -r libreboot.rom If you are told to specify the chip, add the option **-c {your chip}** to the command, for example: @@ -144,7 +144,7 @@ Extract grubtest.cfg from the ROM image {#extract_testconfig} You can check the contents of the ROM image, inside CBFS: - \$ cd .../libreboot\_util/cbfstool** \$ ./cbfstool libreboot.rom + $ cd .../libreboot\_util/cbfstool** \$ ./cbfstool libreboot.rom print** The files *grub.cfg* and *grubtest.cfg* should be present. grub.cfg is @@ -154,7 +154,7 @@ reduce the possibility of bricking your device, so DO NOT SKIP THIS! Extract grubtest.cfg from the ROM image: - \$ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg + $ ./cbfstool libreboot.rom extract -n grubtest.cfg -f grubtest.cfg Modify the grubtest.cfg accordingly. @@ -166,7 +166,7 @@ Re-insert the modified grubtest.cfg into the ROM image {#reinsert_modified_testc Once your grubtest.cfg is modified and saved, delete the unmodified config from the ROM image: - \$ ./cbfstool libreboot.rom remove -n grubtest.cfg + $ ./cbfstool libreboot.rom remove -n grubtest.cfg Next, insert the modified version: @@ -182,7 +182,7 @@ Testing [../install/#flashrom](../install/#flashrom) for information on how to flash it. - \$ cd /libreboot\_util** # **./flash update libreboot.rom + $ cd /libreboot\_util** # **./flash update libreboot.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: @@ -220,11 +220,11 @@ grub.cfg** Delete the grub.cfg that remained inside the ROM: - \$ ./cbfstool libreboot.rom remove -n grub.cfg + $ ./cbfstool libreboot.rom remove -n grub.cfg Add the modified version that you just made: - \$ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw + $ ./cbfstool libreboot.rom add -n grub.cfg -f grub.cfg -t raw **Now you have a modified ROM. Again, refer back to [../install/#flashrom](../install/#flashrom) for information on how to diff --git a/docs/grub/index.md b/docs/grub/index.md @@ -41,12 +41,12 @@ one](http://sourceforge.net/projects/dejavu/files/dejavu/2.34/dejavu-fonts-ttf-2 This is a free font that is also contained in GNU+Linux distributions like Debian, Devuan or Parabola. - \$ cd libreboot\_src/grub + $ cd libreboot\_src/grub compile grub (the build scripts info on how to do this) come back out into libreboot\_src/resources/grub: - \$ cd ../libreboot\_src/resources/grub/font + $ cd ../libreboot\_src/resources/grub/font I took Dejavu Sans Mono from dejavu (included in this version of libreboot) and did: @@ -73,7 +73,7 @@ Keymaps are stored in resources/utilities/grub-assemble/keymap/. Example (French Azerty): - \$ ckbcomp fr > frazerty + $ ckbcomp fr > frazerty Go in grub directory: @@ -98,7 +98,7 @@ ukdvorak had to be created manually, based on usdvorak. diff them (under resources/utilities/grub-assemble/keymap/original) to see how ukdvorak file was created - \$ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb + $ cat ukdvorak | ./grub/grub-mklayout -o ukdvorak.gkb Copyright © 2014 Leah Rowe <info@minifree.org> diff --git a/docs/hcl/gm45_remove_me.md b/docs/hcl/gm45_remove_me.md @@ -38,7 +38,7 @@ ich9gen executables can be found under ./ich9deblob/ statically compiled in libreboot\_util. If you are using src or git, build ich9gen from source with: - \$ ./oldbuild module ich9deblob + $ ./oldbuild module ich9deblob The executable will appear under resources/utilities/ich9deblob/ Run: @@ -70,7 +70,7 @@ onboard ethernet chipset is flashed (inside the ROM image). You should generate a descriptor+gbe image with your own MAC address inside (with the Gbe checksum updated to match). Run: - \$ ./ich9gen \--macaddress XX:XX:XX:XX:XX:XX + $ ./ich9gen \--macaddress XX:XX:XX:XX:XX:XX (replace the XX chars with the hexadecimal chars in the MAC address that you want) @@ -170,7 +170,7 @@ under resources/utilities/ich9deblob/ and will already be compiled if you ran **./oldbuild module all** or **./oldbuild module ich9deblob** from the main directory (./), otherwise you can build it like so: - \$ ./oldbuild module ich9deblob + $ ./oldbuild module ich9deblob An executable file named **ich9deblob** will now appear under resources/utilities/ich9deblob/ diff --git a/docs/hcl/index.md b/docs/hcl/index.md @@ -407,7 +407,7 @@ for whatever reason, since they include a lot of useful information. Backups created using wget: - \$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/ + $ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/ **\$ wget -m -p -E -k -K -np http://macbook.donderklumpen.de/coreboot/** diff --git a/docs/hcl/t500.md b/docs/hcl/t500.md @@ -71,7 +71,7 @@ factory.rom image dumped from the T500 with a SOIC-8 4MiB flash chip. The patch re-creates the X200 descriptor/gbe source, so the commands were something like: - \$ diff -u t500gbe x200gbe + $ diff -u t500gbe x200gbe \$ **diff -u t500descriptor x200descriptor** ME VSCC table is in a different place and a different size on the T500. diff --git a/docs/index.md b/docs/index.md @@ -177,7 +177,7 @@ If it exists, you can also extract this *lbversion* file by using the either dumped or haven't flashed yet. In your distribution, run cbfstool on your ROM image (*libreboot.rom*, in this example): - \$ ./cbfstool libreboot.rom extract -n lbversion -f lbversion + $ ./cbfstool libreboot.rom extract -n lbversion -f lbversion You will now have a file, named *lbversion*, which you can read in whatever program it is that you use for reading/writing text files. diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md @@ -189,8 +189,8 @@ contents of this file with: #!/bin/sh -e ### BEGIN INIT INFO # Provides: led_aging.sh - # Required-Start: \$local_fs - # Required-Stop: \$local_fs + # Required-Start: $local_fs + # Required-Stop: $local_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start LED aging diff --git a/docs/misc/bbb_ehci.md b/docs/misc/bbb_ehci.md @@ -134,13 +134,13 @@ arm-linux-gnueabihf setup on your *host*. <!-- --> - \$ 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: <!-- --> @@ -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 diff --git a/docs/misc/index.md b/docs/misc/index.md @@ -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,12 +215,12 @@ behaviour. Disable or enable beeps when removing/adding the charger: - \$ sudo ./nvramtool -w power\_management\_beeps=Enable + $ 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=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 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 diff --git 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 diff --git a/docs/publish.sh b/docs/publish.sh @@ -7,4 +7,4 @@ echo $FILE cat $FILE.md > temp.md sed temp.md -i -e 's/.md\(#[a-z\-]*\)*)/.html\1)/g' TOC=$(grep -q "^x-toc-enable: true$" temp.md && echo "--toc") -pandoc -t html temp.md -s --css global.css --section-divs -T Libreboot $TOC > $FILE.html +pandoc -t html temp.md -s --css /global.css --section-divs -T Libreboot $TOC > $FILE.html