[Arista] Fix flash size computation for Lodoga #8622
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
The Lodoga platform also matched crow which was hardcoding the flash
size to 3700.
How I did it
By removing the 3700 hardcoding on crow, this change enables autodetect on Clearlake
which in turns allows autodetect for Lodoga.
The threshold was also bumped from 3700 to 4000 because size computation can
differ slightly and report slightly above 3700.
How to verify it
Verify that
docker_inram
is no longer set on/proc/cmdline
Which release branch to backport (provide reason below if selected)
Description for the changelog
Fix flash size computation in boot0 for Lodoga