-
-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Formalise keyboard- and user-specific EEPROM blocks #18874
Conversation
7fd4c6d
to
61fbe0b
Compare
This feels like it's redundant/reproducing the existing kb/user block: qmk_firmware/quantum/eeconfig.h Lines 41 to 42 in 8456978
Probably should see about merging these, at some point? |
These are repurposed when using the data blocks to check validity. At the moment we're storing a version that can be overridden -- if the firmware format of the data segment changes it can be detected in this way. |
c894b0f
to
76aaa96
Compare
a53e5e1
to
109052d
Compare
* Formalise keyboard and user eeconfig datablocks. * Add debounce helper that checks a condition and issues post-write function invocation. * Naming.
* Formalise keyboard and user eeconfig datablocks. * Add debounce helper that checks a condition and issues post-write function invocation. * Naming.
Description
Adds two defines,
EECONFIG_KB_DATA_SIZE
andEECONFIG_USER_DATA_SIZE
which "allocate" areas of EEPROM specifically for keyboard and user usage.Skipped docs, as it's envisaged this will be automatically leveraged by XAP later.
Types of Changes
Checklist