From mboxrd@z Thu Jan 1 00:00:00 1970 From: olof@lixom.net (Olof Johansson) Date: Fri, 16 Aug 2013 09:04:41 -0700 Subject: Broken device trees for exynos in linux-next In-Reply-To: <13b101ce9a14$2cebd700$86c38500$@org> References: <13b101ce9a14$2cebd700$86c38500$@org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Aug 15, 2013 at 5:04 PM, Kukjin Kim wrote: > I think, maybe we discussed about that? :) current exynos_defconfig cannot > support exynos5440 because of LPAE and I remember we decided LPAE and > non-LPAE should be separated. So as I commented before, exynos5440_defconfig > is needed. If you have any concerns, please let me know. Having a SoC-specific defconfig makes no sense. You can run with LPAE enabled on A15 and A7-based systems even if they don't have enough memory to need it. Really, what we want is to just turn on the LPAE functionality and keep everything else common. Forking into two defconfigs seems like the wrong idea, even if we did discuss it before. Having something like a config fragment to include would make more sense, since that could be shared across all platforms (and apply with multi_v7_defconfig for those who want to run that on LPAE as well). Or, you know, just have your build script enable it without having an in-tree config fragment. That'd work too. The main case where this isn't sufficient is on platforms where _all_ memory sits above 4G, since you can't boot a non-LPAE kernel on those at all. It seems like 5440 has memory starting at 2GB so it's not one of those. -Olof