-
Notifications
You must be signed in to change notification settings - Fork 16.8k
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
Feature/fix storagemanager layout size #10391
Conversation
Isn't this going to stuff people's existing storage? You're effectively modifying the layout. @WickedShell was musing recently we should revisit the way we do storage generally. |
it there a way to check how the layout is ? normally the layout is unchanged, it just correct the storage size reporting that is only calculated on instantiation and then before swtiching to copter layout. It make no sens to instantiate init with one layout and directly change it with another layout... it is better to directly instantiate on the right layout. |
OK, now I've actually gone back and had a thorough read I think I like this. I haven't tested it yet. |
rebase and add static_assert |
How does this relate to #4172 ? |
pending testing on a board with OSD param storage |
@tridge hello, I don't have Osb board. But we should be able to test on SITL, right ? what do you want to test exactly ? |
WITH FIX :
On rover
On master
Rover :
|
@tridge ping on this one ! |
Closed by #13299 |
fix #10389
use compile time option to define storage layout. It solve the issue and reduce the build size.
I also remove the memset as direct initialisation to zero is faster in this case and gain some size.
I move the define to the cpp to reduce scope