On Thu, Aug 27, 2015 at 08:22:36PM +0200, Paul Kocialkowski wrote:
Le vendredi 17 juillet 2015 à 10:57 -0500, Rob Herring a écrit :
If a dtb is specified on the command-line, the Android boot image ramdisk will not be found. Fix this so that we can specify the ramdisk address and dtb address. The syntax is to enter the Android boot image address for both the kernel and ramdisk.
This commit breaks booting non-fdt Android images (the kernel doesn't find the initramfs, and neither does U-Boot).
The test to enter the code block where Android ramdisk support was moved is accessed with: else if (select || genimg_has_config(images)) {
However, in a non-fdt context, select is NULL and genimg_has_config returns 0.
I suggest we either duplicate Android ramdisk support in the non-fdt path or adapt the condition to enter the code block where it was moved.
I've taken a third path, make the code check for Android images and then "know" what the address we want to check should be. Let me know if that patch fixes your problem, thanks!