forked from forks/qmk_firmware
2cb32328b6
* martenwuut's original code commit * delete random directory that is the same as the parent directory * get this compiling * update readmes * add manufacturer * fix up the keymap error and replace KC_A with KC_1 * add verc support which is basically just at trimmed down verb * update keymap readme to specify which redscarf it is * add parent level readme * fix grammar * fix up readmes and put in alternative name for PCBs * add configurator support for the ver.c pcb * add configurator support for Ver.B (RS78) pcb * add iso support for Ver.C (RS68) * change DEBOUNCING_DELAY to just DEBOUNCE * remove K2C to fit the default layouts * fix keymap * fixup configurator layout with split backspace
24 lines
1 KiB
Markdown
Executable file
24 lines
1 KiB
Markdown
Executable file
# Red Scarf II+ Ver.C (RS68)
|
|
|
|
A 65% custom keyboard.
|
|
|
|
Keyboard Maintainer: [MechMerlin](https://github.com/mechmerlin)
|
|
Hardware Supported: Ver.C RS68
|
|
Hardware Availability: [Drop](https://drop.com/buy/red-scarf-ii-ver-b-custom-mechanical-keyboard-kit)
|
|
|
|
Please note that when QMK firmware is flashed, the remote will cease to control the underglow LEDs.
|
|
|
|
## Flashing
|
|
|
|
The flashing is sub-optimal.
|
|
|
|
Flashing the Red Scarf involves using Google Chrome, downloading an extension, and then flashing. For more detailed instructions please refer to [kairyu.gitbooks.io](https://kairyu.gitbooks.io/red-scarf-ii-plus-user-guide-how-to-custom-layout/content/online_reflash.html)
|
|
|
|
---
|
|
|
|
Make example for this keyboard (after setting up your build environment):
|
|
|
|
make redscarf_iiplus/verc:default
|
|
|
|
See the [build environment setup](https://docs.qmk.fm/#/getting_started_build_tools) and the [make instructions](https://docs.qmk.fm/#/getting_started_make_guide) for more information. Brand new to QMK? Start with our [Complete Newbs Guide](https://docs.qmk.fm/#/newbs).
|