Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RESET vs QK_BOOT? #16648

Closed
mcp292 opened this issue Mar 14, 2022 · 6 comments
Closed

RESET vs QK_BOOT? #16648

mcp292 opened this issue Mar 14, 2022 · 6 comments

Comments

@mcp292
Copy link

mcp292 commented Mar 14, 2022

There seems to be two documented ways to put the keyboard in bootloader mode:

  1. RESET.
  2. QK_BOOT.

Which is best practice and what are the differences?

Similarly, EEP_RST vs EE_CLR?

@KarlK90
Copy link
Member

KarlK90 commented Mar 14, 2022

QK_BOOT or QK_BOOTLOADER is the recommended way. Same is true for EE_CLR.

@mcp292
Copy link
Author

mcp292 commented Mar 14, 2022

Thank you. Is this documented somewhere that I missed?

@KarlK90
Copy link
Member

KarlK90 commented Mar 14, 2022

The PR introducing these changes is the best I can find. #15968

@mcp292
Copy link
Author

mcp292 commented Mar 17, 2022

Ah, okay thanks!

@fauxpark based on my experience with these changes, do you think it worthwhile to document these bindings as the new standard and remove the keycodes they replace in the documentation with a note.

@fauxpark
Copy link
Member

fauxpark commented Mar 18, 2022

Not sure how I missed those in the above PR... I know all the existing keymaps, as well as Configurator, also need to be updated to recognise these new names.

@mcp292
Copy link
Author

mcp292 commented Mar 18, 2022

Okay great!

@drashna drashna closed this as completed Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants