mirrors/keychron_qmk_firmware
mirrors/keychron_qmk_firmware
0
0
Fork 0
mirror of https://github.com/Keychron/qmk_firmware.git synced 2024-12-26 11:08:52 +06:00
Code Issues Packages Projects Releases Wiki Activity
e071206c58
keychron_qmk_firmware/keyboards/minidox
History
Danilo de Klerk c8b721d7c6
split_3x5_3 layout support (#9624) 
* Add split_3x5_3 support to Minidox

* Add split_3x5_3 support to Miniaxe

* Add LAYOUT_mini to Centromere

This layout macro removes the need or KC_NO keycodes in the keymap.

* Add split_3x5_3 support to Centromere

* Add split_3x5_3 support to suihankey split

* Add LAYOUT_mini to centromere/info.json

* Add LAYOUT_mini to crkbd

* Add split_3x5_3 support to crkbd

* Change mini layout names

* Rename main layouts for split_3x6_3 keyboards

* Use split_3x5_3 macro for remaining keyboards

* Update relevant info.json files

* Fix suihankey/split/alpha macro

* Add layout aliases for suihankey
2020-08-06 10:36:26 -07:00
..
keymaps split_3x5_3 layout support (#9624) 2020-08-06 10:36:26 -07:00
rev1 split_3x5_3 layout support (#9624) 2020-08-06 10:36:26 -07:00
config.h Refactor minidox to use split_common (#7924) 2020-01-29 17:33:15 -05:00
minidox.c
minidox.h Refactor minidox to use split_common (#7924) 2020-01-29 17:33:15 -05:00
readme.md Refactor minidox to use split_common (#7924) 2020-01-29 17:33:15 -05:00
rules.mk Refactor minidox to use split_common (#7924) 2020-01-29 17:33:15 -05:00

readme.md

MiniDox

MiniDox

A compact version of the ErgoDox

  • Keyboard Maintainer: That-Canadian
  • Hardware Supported: MiniDox PCB rev1 Pro Micro

Make example for this keyboard (after setting up your build environment):

make minidox/rev1:default

Flashing example for this keyboard (using the command line):

make minidox/rev1:default:flash

See build environment setup then the make instructions for more information.

Build Guide

A build guide for putting together the MiniDox v1 can be found here: MiniDox Build Log / Guide

Choosing which board to plug the USB cable into (choosing Master)

Because the two boards are identical, the firmware has logic to differentiate the left and right board. It uses two strategies to figure things out, EE_HANDS or by define. See setting-handedness for more information.