-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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
Clean up EEPROM #17803
Clean up EEPROM #17803
Conversation
812021a
to
cd5301f
Compare
If you are removing |
Thank you for bringing that to my attention here and on the other issue. I had the vague impression that persistent-store implementations already had this covered, but now I see: I still need to migrate some dangling inits over to I've been trying to tread lightly and not modify existing behavior until I had time and space to develop the full picture. I think I'm just about caught up now. |
8a3c5fe
to
7bc2167
Compare
7bc2167
to
29d2865
Compare
It looks like, across the board, the Flash-based EEPROM emulations want to call their |
d8e9887
to
ab5a002
Compare
Looks like they are just following the old pattern then adding a flag in the init function so it only actually happens once. Could only have a quick look, not even sure how the STM32_F4_F7 is handling the flash write buffering without using |
Actually I tried to build default with STM32F4 and I couldn't get past it not grokking our serial class names. I think that HAL is fundamentally fakakta. |
064b384
to
5e3ad0e
Compare
5e3ad0e
to
52d5535
Compare
Ok, this is better in-general. The |
References: #17651, #17772