We've never shipped a device with userland code using OABI afaik, so
this is enabling code paths that is purely bloat. Disable it like we
have for all other arm platforms.
BUG=None
TEST=`emerge-daisy chromeos-kernel` works and doesn't have OABI enabled
Change-Id: Ie8a67b3db7faba3ac430e1de678e60b1fba1ffb5
Signed-off-by: Mike Frysinger <vapier@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/47911
Reviewed-by: Olof Johansson <olofj@chromium.org>
CONFIG_NEON=y
# CONFIG_NET_DMA is not set
CONFIG_NO_IOPORT=y
-CONFIG_OABI_COMPAT=y
# CONFIG_OC_ETM is not set
CONFIG_PAGE_OFFSET=0x80000000
CONFIG_PL330_DMA=y
CONFIG_MMC_SDHCI_PLTFM=y
CONFIG_MMC_SDHCI_TEGRA=y
# CONFIG_NEON is not set
-# CONFIG_OABI_COMPAT is not set
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_MMC_SDHCI_PLTFM=y
CONFIG_MMC_SDHCI_TEGRA=y
# CONFIG_NEON is not set
-# CONFIG_OABI_COMPAT is not set
CONFIG_OUTER_CACHE=y
CONFIG_OUTER_CACHE_SYNC=y
CONFIG_PAGEFLAGS_EXTENDED=y
CONFIG_NF_CONNTRACK_PROCFS=y
CONFIG_NF_CONNTRACK_PROC_COMPAT=y
CONFIG_NR_CPUS=2
+# CONFIG_OABI_COMPAT is not set
CONFIG_OF=y
CONFIG_OF_ADDRESS=y
CONFIG_OF_DEVICE=y