On 17:03 Tue 28 Feb , Stephen Warren wrote: > 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. > > Signed-off-by: Stephen Warren <swarren@xxxxxxxxxx> > --- > I assume I should put this into the ARM patch tracker if it's OK? Again a new option for uImage no why not just boot the zImage in this case the uImage is useless Best Regards, J. -- 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
