66db2e6049
Revert "chore: refactor flash impl"
...
This reverts commit 96a9ae2ca5b0137f50a2f1130326ad1657c719b9.
2022-11-20 21:46:40 -04:00
96a9ae2ca5
chore: refactor flash impl
2022-11-17 10:47:19 -04:00
5d7cf3a8a2
chore: remove util fn for stdlib equivalent
2022-11-11 13:02:51 -04:00
af8ec4db5b
chore: go through TODOs and FIXMEs
...
mainly deleting / rewording those that no longer apply
2022-10-31 06:17:09 -03:00
b5d8a65e69
style(backup): refactor code
2022-10-10 12:01:49 -03:00
8028394105
style(flash): move flash code into it's own file
2022-10-10 12:01:49 -03:00
cb0eb67e4b
style(eeprom): move eeprom code to it's own file
2022-10-10 12:00:45 -03:00
92cfc763c0
chore: move util.zig
2022-09-19 16:07:19 -03:00
4af144fca2
fix: Detect FRAM ROMs
2022-09-18 06:19:05 -03:00
9a8aaba1ab
chore: improve util and Gui API
2022-09-18 05:55:15 -03:00
19d78b9292
feat: auto-detect RTC in commercial ROMS
2022-09-17 20:23:49 -03:00
3fb7f2f814
chore: better conform to zig idioms
2022-09-03 18:30:48 -03:00
5f8c6833f4
chore: improve init/deinit methods
2022-08-29 01:07:25 -05:00
aa52bb5917
chore: reorganize some code
2022-08-26 14:13:49 -05:00
e57f918856
chore: pass the allocator as an argument more often
...
As of right now, I think the only cases where I shouldn't explicitly pass an allocator
are in read/write functions and deinits
2022-08-26 13:54:38 -05:00
e5b7441740
fix: resolve use-afer-free in backup.zig
...
This worked fine on stage1, and works fine in debug in stage3.
However, stage3 ReleaseSafe would panic due to what I assume must
have been an undefined behaviour optimization.
While I'm happy that I was quickly made aware of the issue thanks to
the safety checks in ReleaseSafe I do wish that this issue showed itself
in Debug, since I *am* using the GPA
2022-08-26 13:04:09 -05:00
739db99c83
fix: reimpl debug reads w/out throwing away *const Self
2022-08-07 05:11:29 -05:00
53191b0eeb
chore: change directory structure
2022-07-22 21:11:19 -03:00
