edk2.py: Improve firmware volume (de)serialization #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I added a few test cases to the repo which fail with this pull request applied. Would you mind to have a look? :) |
- The last field of the firmware volume header is a variable size, run-length encoded blockmap, we cannot and shouldn't hardcode this. - The length of the firmware volume header can be variable and is described by the `HeaderLength` field. - Firmware volumes can have so called "extension headers", we don't understand these, thus it is likely better to error out then produce bad data when encountering them. Signed-off-by: Mate Kukri <mate.kukri@canonical.com>
|
Thank you! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
HeaderLengthfield.