diff options
author | Jack Humbert <jack.humb@gmail.com> | 2015-10-27 00:48:22 -0400 |
---|---|---|
committer | Jack Humbert <jack.humb@gmail.com> | 2015-10-27 00:48:22 -0400 |
commit | 5a268d97ec36e97c871b601795105f02999356ab (patch) | |
tree | df6823665581623ae574a7450f8968fc58653171 /keyboard | |
parent | a6913550c8a1c7e6e77c895b6006de79a25e3aee (diff) | |
download | firmware-5a268d97ec36e97c871b601795105f02999356ab.tar.gz firmware-5a268d97ec36e97c871b601795105f02999356ab.tar.bz2 firmware-5a268d97ec36e97c871b601795105f02999356ab.zip |
READMEs
Diffstat (limited to 'keyboard')
-rw-r--r-- | keyboard/planck/PCB_GUIDE.md | 15 | ||||
-rw-r--r-- | keyboard/planck/README.md | 2 |
2 files changed, 9 insertions, 8 deletions
diff --git a/keyboard/planck/PCB_GUIDE.md b/keyboard/planck/PCB_GUIDE.md index 88a6c0140..10b86bb3b 100644 --- a/keyboard/planck/PCB_GUIDE.md +++ b/keyboard/planck/PCB_GUIDE.md @@ -8,16 +8,17 @@ 3. Start DFU bootloader on the chip first time you will see 'Found New Hardware Wizard' to install driver. If you install device driver properly you can find chip name like 'ATmega32U4' under 'LibUSB-Win32 Devices' tree on 'Device Manager'. If not you will need to update its driver on 'Device Manager' to the `dfu-programmer` driver. ### Mac -1. Install [CrossPack](http://www.obdev.at/products/crosspack/index.html) or install Xcode from the App Store and install the Command Line Tools from `Xcode->Preferences->Downloads`. -2. Install [DFU-Programmer][dfu-prog]. +1. Install Xcode from the App Store. +2. Install the Command Line Tools from `Xcode->Preferences->Downloads`. +3. Install [DFU-Programmer][dfu-prog]. ### Linux 1. Install AVR GCC with your favorite package manager. 2. Install [DFU-Programmer][dfu-prog]. -##Verify Your Installation -1. Clone the following repository: https://github.com/jackhumbert/tmk_keyboard -2. Open a Terminal and `cd` into `tmk_keyboard/keyboard/planck` +## Verify Your Installation +1. Clone the following repository: https://github.com/jackhumbert/qmk_firmware +2. Open a Terminal and `cd` into `qmk_firmware/keyboard/planck` 3. Run `make`. This should output a lot of information about the build process. ## Using the built-in functions @@ -38,11 +39,11 @@ Generally, the instructions to flash the PCB are as follows: 4. Press the reset button on the PCB/press the key with the `RESET` keycode 5. `make <arguments> dfu` - use the necessary `KEYMAP=<keymap>` and/or `COMMON=true` arguments here. -## OLKB keymap +## Quantum MK Firmware ### Keymap -Unlike the other keymaps, prefixing the keycodes with `KC_` is required. A full list of the keycodes is available [here](https://github.com/jackhumbert/tmk_keyboard/blob/master/doc/keycode.txt). For the keycodes available only in the extended keymap, see this [header file](https://github.com/jackhumbert/tmk_keyboard/blob/master/keyboard/planck/keymap_common.h). +Unlike the other keymaps, prefixing the keycodes with `KC_` is required. A full list of the keycodes is available [here](https://github.com/jackhumbert/qmk_firmware/blob/master/doc/keycode.txt). For the keycodes available only in the extended keymap, see this [header file](https://github.com/jackhumbert/qmk_firmware/blob/master/quantum/keymap_common.h). You can use modifiers with keycodes like this: diff --git a/keyboard/planck/README.md b/keyboard/planck/README.md index faaee0958..a733f0793 100644 --- a/keyboard/planck/README.md +++ b/keyboard/planck/README.md @@ -2,7 +2,7 @@ Planck keyboard firmware ====================== DIY/Assembled compact ortholinear 40% keyboard by [Ortholinear Keyboards](http://ortholinearkeyboards.com). -## OLKB Keymap +## Quantum MK Firmware You have access to a bunch of goodies: - Use `LSFT()`, `LCTL()`, et. al. (listed in keymap_common.h) as modifiers for keys (daisy-chain-able) |