Skip to content

Make it compatible with latest QMK (0.29.12)#4

Open
gwangyi wants to merge 11 commits intoEpomaker:mainfrom
gwangyi:upstream
Open

Make it compatible with latest QMK (0.29.12)#4
gwangyi wants to merge 11 commits intoEpomaker:mainfrom
gwangyi:upstream

Conversation

@gwangyi
Copy link
Copy Markdown

@gwangyi gwangyi commented Aug 7, 2025

No description provided.

gwangyi added 7 commits August 6, 2025 21:56
The top-left key matrix was 1,0, not 0,0.
For the right-half, you can use -> key to enter DFU.
Low power battery saving is not working correctly. When the timeout
comes, keyboard stuck forever.

To use the keyboard, temporarily I disabled it.
1. EECONFIG_USER_DATABLOCK is no longer exposed.
   Replaced with public APIs nvm_eeconfig_(read|update)_user_datablock().
2. Explicitly define UART related macros.
   qmk/qmk_firmware#24855 removed some of
   deprecated macros and it breaks wireless functionality.
3. keyboard_protocol is no longer exposed.
   Replaced with public APIs usb_device_state_(set|get)_protocol().
4. Synced a raw_hid() call site in via.c.
5. eeconfig_(read|update)_keymap() has been changed.
@pcm2a
Copy link
Copy Markdown

pcm2a commented Sep 6, 2025

@gwangyi saw a comment about getting sleep/wakeup to work in split65.c. Does low power mode work?
return false; // TODO: figure out why sleep/wakeup doesn't working

@gwangyi
Copy link
Copy Markdown
Author

gwangyi commented Sep 12, 2025

I couldn't figure out yet, but I can say the keyboard isn't waking up after entering low power mode. Also RGB matrix get stuck when it enters into the low power mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants