Stephen Warren wrote at Tuesday, February 28, 2012 5:03 PM: > uImage files typically encode a single absolute load and entry address. > This is inconvenient when attempting to share that uImage across multiple > SoCs with different physical RAM addresses. Recent versions of mkimage > implement a "kernel_noload" image type which encodes no absolute load > address, and a relative entry address. This works well for uImage-wrapped > ARM zImages, since they are relocatable. > > This is enabled by commit b9b50e89d317c58becd0e2d7fac2e21e3a81dd0a > "image: Implement IH_TYPE_KERNEL_NOLOAD" in U-Boot. So Russell, are you NAKing this patch then? If so, I guess I'll just go and add more cruft to my copy-a-kernel-to- an-sd-card script. Which is a pity since every other person will have to do the same, but oh well. -- nvpublic -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
