Re: Broken device trees for exynos in linux-next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 15, 2013 at 5:04 PM, Kukjin Kim <kgene@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux SoC Development]     [Linux Rockchip Development]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Linux SCSI]     [Yosemite News]

  Powered by Linux