1
0
Fork 0
forked from forks/qmk_firmware
Commit graph

12 commits

Author SHA1 Message Date
Ryan 47966dc2a6
Migrate rgblight.pin and RGB_DI_PIN to ws2812.pin (#20303) 2023-04-06 18:00:54 +10:00
Ryan 65a80f411f
Clean up APA102 config and add DD mapping (#20159) 2023-03-20 08:12:19 +11:00
Nick Brassel 9d302f9b7f
Fixup CI build for F103C6 onekey. (#20188) 2023-03-19 20:33:21 +00:00
Ryan 499fc3b85e
Add some missing #pragma onces (#19902) 2023-02-21 15:55:23 +00:00
Nick Brassel f6dd8dea2e
Remove usages of config_common.h from config.h files. (#19714) 2023-01-31 06:03:30 +11:00
QMK Bot 8449a4a11f Merge remote-tracking branch 'origin/master' into develop 2022-11-18 02:17:25 +00:00
Joel Challis 5d882ab6ef
Disable onekey console by default (#19104) 2022-11-18 02:16:38 +00:00
Ryan 8cecf7fad8
onekey: disable NKRO and mousekeys by default (#19038) 2022-11-12 03:20:44 +00:00
Ryan e0115caab9
onekey: enable ADC for Bluepill and Blackpill (#18545) 2022-09-30 17:14:41 +01:00
Ryan 45b5ed5c6e
Onekey: migrate some stuff to data driven (#18502) 2022-09-30 04:23:11 +10:00
Ryan cf41c24db8
Move keyboard USB IDs and strings to data driven: develop (#18152)
* Move keyboard USB IDs and strings to data driven: develop

* Also do new onekeys
2022-08-24 15:28:38 +01:00
Sergey Vlasov 9e44362179
Add minimal STM32F103C6 support (#17853)
Unfortunately, the crippled versions of “Bluepill” boards with
STM32F103C6xx chips instead of STM32F103C8xx are now sold all over the
place, sometimes advertised in a confusing way to make the difference
not noticeable until too late.  Add minimal support for these MCUs in
the common “Bluepill with stm32duino” configuration, so that it could be
possible to make something useful from those boards (although fitting
QMK into the available 24 KiB of flash may be rather hard).

(In fact, I'm not sure whether the “STM32” part of the chip name is
actually correct for those boards of uncertain origin, so the onekey
board name is `bluepill_f103c6`; another reason for that name is to
match the existing `blackpill_f401` and `blackpill_f411`.)

The EEPROM emulation support is not included on purpose, because
enabling it without having a working firmware size check would be
irresponsible with such flash size (the chance that someone would build
a firmware where the EEPROM backing store ends up overlapping some
firmware code is really high).  Other than that, enabling the EEPROM
emulation code is mostly trivial (the `wear_leveling` driver with the
`embedded_flash` backing store even works without any custom
configuration, although its code is significantly larger than the
`vendor` driver, which may also be important for such flash size).
2022-08-11 22:37:41 +01:00