summaryrefslogtreecommitdiff
path: root/keyboards/wilba_tech/wt70_jb
diff options
context:
space:
mode:
authorWilba <wilba@wilba.tech>2022-08-10 13:01:09 +1000
committerGitHub <noreply@github.com>2022-08-09 20:01:09 -0700
commit8a24fbbdaea4f3ff9bdcdf76036bedca6e335bce (patch)
tree022f2696570a1b564daa36d8bed3df22cf960307 /keyboards/wilba_tech/wt70_jb
parent7019d0bce890ca97937d62e843adcdc9b9a0d1fd (diff)
Fix detection of EEPROM reset in some keyboards (#17970)
Diffstat (limited to 'keyboards/wilba_tech/wt70_jb')
-rw-r--r--keyboards/wilba_tech/wt70_jb/wt70_jb.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/keyboards/wilba_tech/wt70_jb/wt70_jb.c b/keyboards/wilba_tech/wt70_jb/wt70_jb.c
index 0bb9aca092..d4f2c5c8da 100644
--- a/keyboards/wilba_tech/wt70_jb/wt70_jb.c
+++ b/keyboards/wilba_tech/wt70_jb/wt70_jb.c
@@ -38,9 +38,9 @@ bool led_update_kb(led_t led_state) {
// Called from matrix_init_kb() if not VIA_ENABLE
void via_init_kb(void)
{
- // If the EEPROM has the magic, the data is good.
- // OK to load from EEPROM
- if (via_eeprom_is_valid()) {
+ // This checks both an EEPROM reset (from bootmagic lite, keycodes)
+ // and also firmware build date (from via_eeprom_is_valid())
+ if (eeconfig_is_enabled()) {
} else {
// Cache "first execution" state so we can do something
// specific after QMK initialization has done its thing.