| Age | Commit message (Collapse) | Author |
|---|
|
These are the defaults for x86 and x86_64 when doing a defconfig
on those arch with the kernel.org tree. Ours might as well be
the same values.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
|
|
In mainline defconfigs we have:
arch/x86/configs/i386_defconfig:# CONFIG_MTRR_SANITIZER is not set
arch/x86/configs/x86_64_defconfig:# CONFIG_MTRR_SANITIZER is not set
But the defaults given by the Kconfig stanza are "def_bool y" so
if we want to match the defconfigs, we need to call it out as off
explicitly.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The default x86[64] defconfig on a kernel.org 3.4 tree will have these
enabled. Since we can't be sure we'll be running on a platform
with or without these issues, it makes sense for us to have them
enabled here as well.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Currently, BSPs like common-pc differ from the korg x86 defconfig
as follows:
common_pc x86 korg defconfig
------------------------------------------------------------------
CONFIG_VMSPLIT_3G=y
# CONFIG_VMSPLIT_3G_OPT is not set
# CONFIG_VMSPLIT_2G is not set
# CONFIG_VMSPLIT_2G_OPT is not set
# CONFIG_VMSPLIT_1G is not set
# CONFIG_HIGHPTE is not set CONFIG_HIGHPTE=y
Given that machines with 4G or more RAM are nothing at all unique
anymore, lets align ourselves with enabling HIGHPTE.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Comparing a common-pc config to kernel.org x86 defconfig
reveals this difference:
--- common-pc --- --- korg defconfig ---
# CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS is not set CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
# CONFIG_X86_REBOOTFIXUPS is not set CONFIG_X86_REBOOTFIXUPS=y
# CONFIG_MICROCODE_AMD is not set CONFIG_MICROCODE_AMD=y
Align the x86 defaults with what is in kernel.org, since we've no
real justification for not doing so.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
There will be a significant amount of cfg data that is common
across all x86 BSPs. Make a landing ground for it here, similar
to what ARM has, so that we don't duplicate a bunch of stuff
in every x86 BSP file.
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
Paul Gortmaker