ARM: imx_v6_v7_defconfig: Remove CONFIG_VMSPLIT_2G
Subsystems (2)
PATCH 1/1 ARM: imx_v6_v7_defconfig: Remove CONFIG_VMSPLIT_2G
CONFIG_VMSPLIT_2G was added to mx5_defconfig by commit 06965c39b4c639 ("ARM i.MX5: update defconfig") to fix an issue where mx53 was not detecting the full 1GiB memory range.
However, as explained by Russell King [1] the correct fix is to select CONFIG_HIGHMEM.
imx_v6_v7_deconfig inherited such option from mx5_defconfig.
As imx_v6_v7_deconfig has CONFIG_HIGHMEM=y, we should no longer select such non-standard CONFIG_VMSPLIT_2G option.
[1] http://www.spinics.net/lists/arm-kernel/msg137839.html
--- arch/arm/configs/imx_v6_v7_defconfig | 1 - 1 file changed, 1 deletion(-)
arch/arm/configs/imx_v6_v7_defconfig +0 -1
@@ -47,7 +47,6 @@ CONFIG_SOC_VF610=y CONFIG_PCI=y CONFIG_PCI_IMX6=y CONFIG_SMP=y -CONFIG_VMSPLIT_2G=y CONFIG_PREEMPT_VOLUNTARY=y CONFIG_AEABI=y CONFIG_HIGHMEM=y
Signature · 1 line
1.9.1
Shawn Guo
AppliedPATCH 1/1 ARM: imx_v6_v7_defconfig: Remove CONFIG_VMSPLIT_2G
Quoted 7 lines · Fabio Estevam
CONFIG_VMSPLIT_2Gwas added tomx5_defconfigby commit06965c39b4c639("ARM i.MX5: update defconfig") to fix an issue where mx53 was not detecting the full 1GiB memory range.However, as explained by Russell King [1] the correct fix is to select
CONFIG_HIGHMEM.
Quoted 8 lines
imx_v6_v7_deconfiginherited such option frommx5_defconfig.As
imx_v6_v7_deconfighasCONFIG_HIGHMEM=y, we should no longer select such non-standardCONFIG_VMSPLIT_2Goption.[1] http://www.spinics.net/lists/arm-kernel/msg137839.html
Signed-off-by Fabio Estevam <[email protected]>
Applied, thanks.