qmk_firmware/keyboards/akegata_denki/device_one
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
..
keymaps
chconf.h
config.h
device_one.c
device_one.h
halconf.h
info.json Migrate `LAYOUTS` to data driven (#19541) 2023-01-10 02:48:20 +00:00
mcuconf.h
readme.md
rules.mk Migrate `LAYOUTS` to data driven (#19541) 2023-01-10 02:48:20 +00:00

readme.md

明け方電気 (akegata denki) device one

device one

A caseless 60% mechanical keyboard that strikes the right balance between affordability and function.

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

make akegata_denki/device_one:default

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