qmk/qmk_firmware
GitHub で見る[Bug] Enabling both VIA support and Joystick support causes unexpected behavior
Open
#20,976 opened on 2023年5月17日
bughelp wanted
Repository metrics
- Stars
- (20,368 stars)
- PR merge metrics
- (平均マージ 20d 9h) (30d で 27 merged PRs)
説明
Describe the Bug
When setting both
VIA_ENABLE = yes
and
JOYSTICK_ENABLE = yes
in rules.mk
VIA works as expected, however, the joystick is detected but not setup properly.
With VIA disabled, the joystick shows up and functions as expected.
Confirmed against multiple Windows environments, and have confirmed that this behavior is not specific to only my device.
Keyboard Used
katana60/rev1
Link to product page (if applicable)
No response
Operating System
Windows
qmk doctor Output
Ψ QMK Doctor is checking your environment.
Ψ CLI version: 1.1.0
Ψ QMK home: /home/soup/git/qmk_firmware
Ψ Detected Linux (WSL, Fedora Remix for WSL).
Ψ Git branch: master
Ψ Repo version: 0.20.8
⚠ Git has unstashed/uncommitted changes.
⚠ The official repository does not seem to be configured as git remote "upstream".
Ψ All dependencies are installed.
Ψ Found arm-none-eabi-gcc version 11.1.0
Ψ Found avr-gcc version 11.2.0
⚠ We do not recommend avr-gcc newer than 8. Downgrading to 8.x is recommended.
Ψ Found avrdude version 6.4
Ψ Found dfu-programmer version 0.7.2
Ψ Found dfu-util version 0.11
Would you like to clone the submodules? [Y/n] n
Ψ Submodule status:
Ψ - lib/chibios: 2021-12-08 11:37:03 +0000 -- (257302333)
Ψ - lib/chibios-contrib: 2022-04-18 12:52:47 +0200 -- (2a6b73ff)
Ψ - lib/googletest: 2021-06-11 06:37:43 -0700 -- (e2239ee6)
Ψ - lib/lufa: 2021-07-31 15:44:44 +1000 -- (19a5d533f)
Ψ - lib/vusb: 2020-08-16 01:07:21 +0100 -- (bdb53e4)
Ψ - lib/printf: 2020-01-01 18:16:48 +0100 -- (d3b9846)
Ψ - lib/pico-sdk: 2023-02-12 20:19:37 +0100 -- (a3398d8)
Ψ - lib/lvgl: 2022-04-11 04:44:53 -0600 -- (e19410f)
Ψ QMK is ready to go, but minor problems were found
Is AutoHotKey / Karabiner installed
- AutoHotKey (Windows)
- Karabiner (macOS)
Other keyboard-related software installed
No response
Additional Context
No response