abootimg: Improve compatability with no-initrd abootimg configs

[johnstultz-work]

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

[temoto]

This patch is required to work with stock OrangePi images. Please merge.

[lag-linaro]

Could someone merge this PR please?

It fixes a severe issue when working with current Android images.

LGTM - +1

[phhusson]

"someone".
You do realize this is a one-people project they do (well did it looks like) on their free time?
And there has been no commit since 2012 just saying "please merge" will probably not cut it.

I understand your corporate want this, I think you can feel free to fork it and maintain it.

Also "current Android images" doesn't need this because of Android Q's first-stage init.

If I'm not mistaken, this is required exclusively on Android Pie devices running system-as-root without A/B slots.

[lag-linaro]

"someone".
You do realize this is a one-people project they do (well did it looks like) on their free time?

Yes.

And there has been no commit since 2012 just saying "please merge" will probably not cut it.

I see that. It doesn't mean they won't take a few minutes out of their time to press "merge".

I understand your corporate want this, I think you can feel free to fork it and maintain it.

This doesn't have anything to do with "my corporate".

Also "current Android images" doesn't need this because of Android Q's first-stage init.

If I'm not mistaken, this is required exclusively on Android Pie devices running system-as-root without A/B slots.

Okay, good to know. It's still required for certain use-cases though.