On Wed, Apr 16, 2014 at 10:36:11PM +0100, Peter Maydell wrote: > On 16 April 2014 22:08, Christopher Covington <cov@xxxxxxxxxxxxxx> wrote: > > On 04/16/2014 03:14 PM, Nicolas Pitre wrote: > >> But both QEMU and the boot-wrapper should deal with zImage. That's the > >> only image format with documented load offset is guaranteed not to > >> change i.e. it can be loaded at about any offset as zImage knows how to > >> relocate itself as needed. There is nowhere a guarantee that > >> TEXT_OFFSET can't change. > > > > QEMU definitely does support zImage and I believe it's promoted as the main > > boot method. > > Yes; we also support uImage. The code nominally handling Image > actually currently loads at 0x10000, so the set of people who actually > try to use it is obviously not very large :-) For ARM, that means precisely zero users without modification of that. We've never supported an offset of 0x10000 in mainline kernels. -- FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly improving, and getting towards what was expected from it. -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
