masq
/
qmk_firmware
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
qmk_firmware/keyboards/bastardkb/tbkmini
History
Ryan 56555c61e1
Migrate `LAYOUTS` to data driven (#19541) 
* Migrate `LAYOUTS` to data driven, 0-9

* Migrate `LAYOUTS` to data driven, A

* Migrate `LAYOUTS` to data driven, B

* Migrate `LAYOUTS` to data driven, C

* Migrate `LAYOUTS` to data driven, D

* Migrate `LAYOUTS` to data driven, E

* Migrate `LAYOUTS` to data driven, F

* Migrate `LAYOUTS` to data driven, G

* Migrate `LAYOUTS` to data driven, H

* Migrate `LAYOUTS` to data driven, handwired

* Migrate `LAYOUTS` to data driven, I

* Migrate `LAYOUTS` to data driven, J

* Migrate `LAYOUTS` to data driven, K

* Migrate `LAYOUTS` to data driven, L

* Migrate `LAYOUTS` to data driven, M

* Migrate `LAYOUTS` to data driven, N

* Migrate `LAYOUTS` to data driven, O

* Migrate `LAYOUTS` to data driven, P

* Migrate `LAYOUTS` to data driven, Q

* Migrate `LAYOUTS` to data driven, R

* Migrate `LAYOUTS` to data driven, S

* Migrate `LAYOUTS` to data driven, T

* Migrate `LAYOUTS` to data driven, U

* Migrate `LAYOUTS` to data driven, V

* Migrate `LAYOUTS` to data driven, W

* Migrate `LAYOUTS` to data driven, X

* Migrate `LAYOUTS` to data driven, Y

* Migrate `LAYOUTS` to data driven, Z
 		2023-01-10 02:48:20 +00:00
..
blackpill Migrate `LAYOUTS` to data driven (#19541) 2023-01-10 02:48:20 +00:00
keymaps/default
…
v1/elitec Migrate `LAYOUTS` to data driven (#19541) 2023-01-10 02:48:20 +00:00
v2 Migrate `LAYOUTS` to data driven (#19541) 2023-01-10 02:48:20 +00:00
config.h Change `RGB_MATRIX_STARTUP_*` defines to `RGB_MATRIX_DEFAULT_*` (#19079) 2022-11-27 04:18:24 +11:00
info.json Migrate `LAYOUTS` to data driven (#19541) 2023-01-10 02:48:20 +00:00
readme.md Bastard Keyboards: upstream recent changes (#18903) 2022-11-15 08:51:44 +00:00
tbkmini.c Bastard Keyboards: upstream recent changes (#19083) 2022-11-20 12:34:42 -08:00
tbkmini.h
…

readme.md

TBK Mini

A split, compact ergonomic keyboard.

Building the firmware

You must specify the shield version when compiling/flashing the firmware.

The template is:

qmk compile -kb bastardkb/tbkmini/{VERSION}/elitec -km {KEYMAP}
Shield Version default via
v1 (Elite-C) qmk compile -kb bastardkb/tbkmini/v1/elitec -km default qmk compile -kb bastardkb/tbkmini/v1/elitec -km via
v2 (Elite-C) qmk compile -kb bastardkb/tbkmini/v2/elitec -km default qmk compile -kb bastardkb/tbkmini/v2/elitec -km via
v2 (Splinky v2) qmk compile -kb bastardkb/tbkmini/v2/splinky/v2 -km default qmk compile -kb bastardkb/tbkmini/v2/splinky/v2 -km via
v2 (Splinky v3) qmk compile -kb bastardkb/tbkmini/v2/splinky/v3 -km default qmk compile -kb bastardkb/tbkmini/v2/splinky/v3 -km via
v2 (STeMCell) qmk compile -kb bastardkb/tbkmini/v2/stemcell -km default qmk compile -kb bastardkb/tbkmini/v2/stemcell -km via

See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.

See the keyboard build instructions