abootimg: Improve compatability with no-initrd abootimg configs #3
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.
With newer AOSP devices, system can be used as rootfs, resulting
in no initrd being used in the bootimg.
Without this patch, 'abootimg -x' on such an image would result
with:
/home/jstultz/noinitrd-boot.img: ramdisk size is null
/home/jstultz/noinitrd-boot.img: not a valid Android Boot Image.
This patch just avoids failing out when we see a null ramdisk size.
Signed-off-by: John Stultz john.stultz@linaro.org