Arnd Bergmann wrote at Friday, October 14, 2011 9:30 AM: ... > You mention that tegra30 will require AUTO_ZRELADDR. Well, just to be clear, here's the situation I think: Tegra20's SDRAM starts at physical address 0. Tegra30's SDRAM starts at physical address 2G. To support that, we could either: a) Introduce a new Kconfig variable for Tegra30, make T20/T30 mutually exclusive, and update arch/arm/mach-tegra/Makefile.boot to set zreladdr etc. based on the new Tegra30 config variable too. Then, there's no need for AUTO_ZRELADDR anywhere. b) Have no new config variable, build a unified T20/T30 kernel, leave Makefile.boot untouched, and rely on using AUTO_ZRELADDR for Tegra30 to account for the different SDRAM physical addresses. > Does that mean that with tegra30 merged you would no longer be able > to build any tegra kernel? Sorry, I don't quite understand that question. -- 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
