65dd74a674
Implement SDRAM init using the Memory Reference Code (mrc.bin) provided in the board directory and the SDRAM SPD information in the device tree. This also needs the Intel Management Engine (me.bin) to work. Binary blobs everywhere: so far we have MRC, ME and microcode. SDRAM init works by setting up various parameters and calling the MRC. This in turn does some sort of magic to work out how much memory there is and the timing parameters to use. It also sets up the DRAM controllers. When the MRC returns, we use the information it provides to map out the available memory in U-Boot. U-Boot normally moves itself to the top of RAM. On x86 the RAM is not generally contiguous, and anyway some RAM may be above 4GB which doesn't work in 32-bit mode. So we relocate to the top of the largest block of RAM we can find below 4GB. Memory above 4GB is accessible with special functions (see physmem). It would be possible to build U-Boot in 64-bit mode but this wouldn't necessarily provide any more memory, since the largest block is often below 4GB. Anyway U-Boot doesn't need huge amounts of memory - even a very large ramdisk seldom exceeds 100-200MB. U-Boot has support for booting 64-bit kernels directly so this does not pose a limitation in that area. Also there are probably parts of U-Boot that will not work correctly in 64-bit mode. The MRC is one. There is some work remaining in this area. Since memory init is very slow (over 500ms) it is possible to save the parameters in SPI flash to speed it up next time. Suspend/resume support is not fully implemented, or at least it is not efficient. With this patch, link boots to a prompt. Signed-off-by: Simon Glass <sjg@chromium.org>
93 lines
2.2 KiB
Plaintext
93 lines
2.2 KiB
Plaintext
menu "x86 architecture"
|
|
depends on X86
|
|
|
|
config SYS_ARCH
|
|
default "x86"
|
|
|
|
config USE_PRIVATE_LIBGCC
|
|
default y
|
|
|
|
choice
|
|
prompt "Target select"
|
|
|
|
config TARGET_COREBOOT
|
|
bool "Support coreboot"
|
|
help
|
|
This target is used for running U-Boot on top of Coreboot. In
|
|
this case Coreboot does the early inititalisation, and U-Boot
|
|
takes over once the RAM, video and CPU are fully running.
|
|
U-Boot is loaded as a fallback payload from Coreboot, in
|
|
Coreboot terminology. This method was used for the Chromebook
|
|
Pixel when launched.
|
|
|
|
config TARGET_CHROMEBOOK_LINK
|
|
bool "Support Chromebook link"
|
|
help
|
|
This is the Chromebook Pixel released in 2013. It uses an Intel
|
|
i5 Ivybridge which is a die-shrink of Sandybridge, with 4GB of
|
|
SDRAM. It has a Panther Point platform controller hub, PCIe
|
|
WiFi and Bluetooth. It also includes a 720p webcam, USB SD
|
|
reader, microphone and speakers, display port and 32GB SATA
|
|
solid state drive. There is a Chrome OS EC connected on LPC,
|
|
and it provides a 2560x1700 high resolution touch-enabled LCD
|
|
display.
|
|
|
|
endchoice
|
|
|
|
config RAMBASE
|
|
hex
|
|
default 0x100000
|
|
|
|
config RAMTOP
|
|
hex
|
|
default 0x200000
|
|
|
|
config XIP_ROM_SIZE
|
|
hex
|
|
default 0x10000
|
|
|
|
config CPU_ADDR_BITS
|
|
int
|
|
default 36
|
|
|
|
config HPET_ADDRESS
|
|
hex
|
|
default 0xfed00000 if !HPET_ADDRESS_OVERRIDE
|
|
|
|
config SMM_TSEG
|
|
bool
|
|
default n
|
|
|
|
config SMM_TSEG_SIZE
|
|
hex
|
|
|
|
config ROM_SIZE
|
|
hex
|
|
default 0x800000
|
|
|
|
config HAVE_INTEL_ME
|
|
bool "Platform requires Intel Management Engine"
|
|
help
|
|
Newer higher-end devices have an Intel Management Engine (ME)
|
|
which is a very large binary blob (typically 1.5MB) which is
|
|
required for the platform to work. This enforces a particular
|
|
SPI flash format. You will need to supply the me.bin file in
|
|
your board directory.
|
|
|
|
config X86_RAMTEST
|
|
bool "Perform a simple RAM test after SDRAM initialisation"
|
|
help
|
|
If there is something wrong with SDRAM then the platform will
|
|
often crash within U-Boot or the kernel. This option enables a
|
|
very simple RAM test that quickly checks whether the SDRAM seems
|
|
to work correctly. It is not exhaustive but can save time by
|
|
detecting obvious failures.
|
|
|
|
source "arch/x86/cpu/ivybridge/Kconfig"
|
|
|
|
source "board/chromebook-x86/coreboot/Kconfig"
|
|
|
|
source "board/google/chromebook_link/Kconfig"
|
|
|
|
endmenu
|