- 
                Notifications
    You must be signed in to change notification settings 
- Fork 834
bootutil: Unify app_max_size() implementations #2318
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
bootutil: Unify app_max_size() implementations #2318
Conversation
0a7e9a6    to
    84cf14a      
    Compare
  
    84cf14a    to
    ade4b0d      
    Compare
  
    f7abf5d    to
    c06e0c3      
    Compare
  
    f68249e    to
    862d9fa      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
swap using move/offset OK, no clue about swap using scratch, defer to @taltenbach
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes regarding swap-scratch LGTM, only minor comments. Thanks for the detailed explanation in app_max_size_adjust_to_trailer, it's now much clearer than before!
Remove redundant application size calculations in favor of a swap-specific function, implemented inside swap_<type>.c. In this way, slot sizes use the same restrictions as image validation. Signed-off-by: Tomasz Chyrowicz <[email protected]>
862d9fa    to
    5254b75      
    Compare
  
    | LGTM, @tomchy feel free resolve all open threads (I can't do it myself) | 
Remove redundant application size calculations in favor of a swap-specific function, implemented inside
swap_<type>.c. In this way, slot sizes use the same restrictions as image validation.This change is a follow-up PR to the discussion in the #2283.