From 8a24fbbdaea4f3ff9bdcdf76036bedca6e335bce Mon Sep 17 00:00:00 2001 From: Wilba Date: Wed, 10 Aug 2022 13:01:09 +1000 Subject: Fix detection of EEPROM reset in some keyboards (#17970) --- keyboards/wilba_tech/wt70_jb/wt70_jb.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'keyboards/wilba_tech/wt70_jb') 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. -- cgit v1.2.3