On Wed, 7 Mar 2012, Russell King - ARM Linux wrote: > On Wed, Mar 07, 2012 at 04:03:04PM -0500, Nicolas Pitre wrote: > > Well, I do have a patch series getting rid of ZRELADDR entirely, and > > AUTO_ZRELADDR would then become implicit, unless CONFIG_PHYS_OFFSET is > > defined. > > Not possible, unless you're goign to also rip out uImage support. I wish I could. At least this new "noload" option would make uImage compatible with this. That won't help existing u-Boot installations though, which is why I didn't post that patch series yet as I still haven't found a good fallback. > Otherwise, how do we deal with platforms like Versatile Express where > uboot does a funky relocation of data depending on whether the uImage > it's loading is for the low 256MB RAM mapping or the high 1GB RAM > mapping. Doesn't it use AUTO_ZRELADDR? With the newer u-Boot, you'd just load uImage to whatever address and u-Boot won't mess with it. Nicolas -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
