Remove symbolic linked userspace folder (#22548)
Remove userspace keymaps (#22544)
Stub out community layout directory structure (#22545)
New RGB Animations - 4 "Starlight" Animation Variations (#22212)
Cater for ECC failures in EFL wear-leveling. (#19749)
Co-authored-by: Sergey Vlasov <sigprof@gmail.com>
V-USB: implement NKRO (#22398)
V-USB: Add generic `send_report()` function (#22323)
Merge remote-tracking branch 'origin/master' into develop
DC60: Fix 2u Backspace Support (#22533)
Merge remote-tracking branch 'origin/master' into develop
[Keyboard] darkproject/kd83a_bfg_edition (#18416)
* Add files via upload
* [keyboard]
* [Keyboard]
* Delete flash_spi.c
* Delete flash_spi.h
* Delete wb32_spi_master.c
* Delete wb32_spi_master.h
* [Keyboard]
* Resolved requested changes
* Resolved requested changes
* Changed rules.mk file accordingly.
* Resolved changes accordingly.
* Update config.h file and rules.mk file
* Removed eeprom_flash.c file
* Update default/keymap.c file
* Delete keyboards/darkproject/kd83a_bfg_edition directory
* Add keyboard
* Add keyboard
* Delete darkproject/kd83a_bfg_edition directory
* Resolved Changes
* Resolved requested changes
* keyboard
* Add keyboard
* Delete keyboard
* Add keyboard
* Delete keyboards/darkproject/kd87a_bfg_edition directory
* update keymap.c file
* update via/keymap.c, config.h and kd83a_bfg_edition.c files
* Delete keymap.c
* Update via/keymap.c, config.h and kd83a_bfg_edition.c files
* update config.h file
* update keymap.c file
* update keymap.c file
* update config.h
* update kd83a_bfg_edition.c
* Resolved requested changes.
* Delete folder which was added accidentally.
* Update keyboards/darkproject/kd83a_bfg_edition/config.h
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/info.json
* Update keyboards/darkproject/kd83a_bfg_edition/rules.mk
* Update keyboards/darkproject/kd83a_bfg_edition/info.json
* update info.json file
* update config.h file
* Updated requested changes
* update readme.md
* Resolved requested changes
* Update info.json file
* Delete kd83a_bfg_edition.h
* Delete readme.md in default folder
* Update info.json file
* update info.json
* Updated changes
* Updated changes
* Resolved requested changes
* Resolved requested changes
Remove unnecessary driver counts (#22435)
Migrate some dip switch config to info.json (#22437)
Add simpler method for relocating functions to RAM. (#21804)
[CLI] Remove duplicates from search results (#22528)
Move BACKLIGHT_PWM_PERIOD to correct docs section (#22480)
CLI parallel search updates (#22525)
Fix `qmk find` failure due to circular imports (#22523)
There was an import cycle in the Python modules:
- `qmk.build_targets` imported `qmk.cli.generate.compilation_database`;
- importing `qmk.cli.generate.compilation_database` requires
initializing `qmk.cli` first;
- the initialization of `qmk.cli` imported the modules for all CLI
commands;
- `qmk.cli.compile` imported `qmk.build_targets`.
This cycle did not matter in most cases, because `qmk.cli` was imported
first, and in that case importing `qmk.cli.generate.compilation_database`
did not trigger the initialization of `qmk.cli` again. However, there was
one corner case when `qmk.bulld_targets` was getting imported first:
- The `qmk find` command uses the `multiprocessing` module.
- The `multiprocessing` module uses the `spawn` start method on macOS
and Windows.
- When the `spawn` method is used, the child processes initialize
without any Python modules loaded, and the required modules are loaded
on demand by the `pickle` module when receiving the serialized objects
from the main process.
The result was that the `qmk find` command did not work properly on macOS
(and probably Windows too); it reported exceptions like this:
ImportError: cannot import name 'KeyboardKeymapBuildTarget' from partially initialized module 'qmk.build_targets' (most likely due to a circular import)
Moving the offending `qmk.cli.generate.compilation_database` import into
the method which actually uses it fixes the problem.
Azoteq IQS5xx support (#22280)