2009-08-12 17:00:51 +02:00
|
|
|
##
|
2010-01-20 19:44:30 +01:00
|
|
|
## This file is part of the coreboot project.
|
2009-08-12 17:00:51 +02:00
|
|
|
##
|
2012-08-23 09:32:58 +02:00
|
|
|
## Copyright (C) 2012 Alexandru Gagniuc <mr.nuke.me@gmail.com>
|
2010-01-20 19:44:30 +01:00
|
|
|
## Copyright (C) 2009-2010 coresystems GmbH
|
2009-08-12 17:00:51 +02:00
|
|
|
##
|
2010-01-20 19:44:30 +01:00
|
|
|
## This program is free software; you can redistribute it and/or modify
|
|
|
|
|
## it under the terms of the GNU General Public License as published by
|
|
|
|
|
## the Free Software Foundation; version 2 of the License.
|
|
|
|
|
##
|
|
|
|
|
## This program is distributed in the hope that it will be useful,
|
|
|
|
|
## but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
## GNU General Public License for more details.
|
|
|
|
|
##
|
2009-08-12 17:00:51 +02:00
|
|
|
|
2012-04-12 22:00:03 +02:00
|
|
|
mainmenu "coreboot configuration"
|
2009-08-12 17:00:51 +02:00
|
|
|
|
2009-10-05 15:55:28 +02:00
|
|
|
menu "General setup"
|
|
|
|
|
|
2017-04-03 16:38:20 +02:00
|
|
|
config COREBOOT_BUILD
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
2009-10-05 15:55:28 +02:00
|
|
|
config LOCALVERSION
|
2009-10-07 18:15:40 +02:00
|
|
|
string "Local version string"
|
2009-10-05 15:55:28 +02:00
|
|
|
help
|
|
|
|
|
Append an extra string to the end of the coreboot version.
|
|
|
|
|
|
2009-10-07 18:15:40 +02:00
|
|
|
This can be useful if, for instance, you want to append the
|
|
|
|
|
respective board's hostname or some other identifying string to
|
|
|
|
|
the coreboot version number, so that you can easily distinguish
|
|
|
|
|
boot logs of different boards from each other.
|
|
|
|
|
|
2019-06-08 11:28:52 +02:00
|
|
|
config CONFIGURABLE_CBFS_PREFIX
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
Select this to prompt to use to configure the prefix for cbfs files.
|
|
|
|
|
|
2010-02-09 20:35:16 +01:00
|
|
|
config CBFS_PREFIX
|
2019-06-08 11:28:52 +02:00
|
|
|
string "CBFS prefix to use" if CONFIGURABLE_CBFS_PREFIX
|
2010-02-09 20:35:16 +01:00
|
|
|
default "fallback"
|
|
|
|
|
help
|
|
|
|
|
Select the prefix to all files put into the image. It's "fallback"
|
|
|
|
|
by default, "normal" is a common alternative.
|
|
|
|
|
|
2010-03-16 02:17:19 +01:00
|
|
|
choice
|
2012-04-12 22:00:03 +02:00
|
|
|
prompt "Compiler to use"
|
2010-03-16 02:17:19 +01:00
|
|
|
default COMPILER_GCC
|
|
|
|
|
help
|
|
|
|
|
This option allows you to select the compiler used for building
|
|
|
|
|
coreboot.
|
2016-01-19 20:01:09 +01:00
|
|
|
You must build the coreboot crosscompiler for the board that you
|
|
|
|
|
have selected.
|
|
|
|
|
|
|
|
|
|
To build all the GCC crosscompilers (takes a LONG time), run:
|
|
|
|
|
make crossgcc
|
|
|
|
|
|
|
|
|
|
For help on individual architectures, run the command:
|
|
|
|
|
make help_toolchain
|
2010-03-16 02:17:19 +01:00
|
|
|
|
|
|
|
|
config COMPILER_GCC
|
|
|
|
|
bool "GCC"
|
2012-04-12 22:00:03 +02:00
|
|
|
help
|
|
|
|
|
Use the GNU Compiler Collection (GCC) to build coreboot.
|
|
|
|
|
|
|
|
|
|
For details see http://gcc.gnu.org.
|
|
|
|
|
|
2010-03-16 02:17:19 +01:00
|
|
|
config COMPILER_LLVM_CLANG
|
2016-01-19 20:01:09 +01:00
|
|
|
bool "LLVM/clang (TESTING ONLY - Not currently working)"
|
2012-04-12 22:00:03 +02:00
|
|
|
help
|
2016-01-19 20:01:09 +01:00
|
|
|
Use LLVM/clang to build coreboot. To use this, you must build the
|
|
|
|
|
coreboot version of the clang compiler. Run the command
|
|
|
|
|
make clang
|
|
|
|
|
Note that this option is not currently working correctly and should
|
|
|
|
|
really only be selected if you're trying to work on getting clang
|
|
|
|
|
operational.
|
2012-04-12 22:00:03 +02:00
|
|
|
|
|
|
|
|
For details see http://clang.llvm.org.
|
|
|
|
|
|
2010-03-16 02:17:19 +01:00
|
|
|
endchoice
|
|
|
|
|
|
2013-12-29 18:45:23 +01:00
|
|
|
config ANY_TOOLCHAIN
|
|
|
|
|
bool "Allow building with any toolchain"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Many toolchains break when building coreboot since it uses quite
|
|
|
|
|
unusual linker features. Unless developers explicitely request it,
|
|
|
|
|
we'll have to assume that they use their distro compiler by mistake.
|
|
|
|
|
Make sure that using patched compilers is a conscious decision.
|
|
|
|
|
|
2010-03-25 22:45:25 +01:00
|
|
|
config CCACHE
|
2012-04-12 22:00:03 +02:00
|
|
|
bool "Use ccache to speed up (re)compilation"
|
2010-03-25 22:45:25 +01:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Enables the use of ccache for faster builds.
|
2012-04-12 22:00:03 +02:00
|
|
|
|
|
|
|
|
Requires the ccache utility in your system $PATH.
|
|
|
|
|
|
|
|
|
|
For details see https://ccache.samba.org.
|
2010-03-25 22:45:25 +01:00
|
|
|
|
2015-02-26 20:47:19 +01:00
|
|
|
config FMD_GENPARSER
|
|
|
|
|
bool "Generate flashmap descriptor parser using flex and bison"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Enable this option if you are working on the flashmap descriptor
|
|
|
|
|
parser and made changes to fmd_scanner.l or fmd_parser.y.
|
|
|
|
|
|
|
|
|
|
Otherwise, say N to use the provided pregenerated scanner/parser.
|
|
|
|
|
|
2017-04-10 03:12:42 +02:00
|
|
|
config UTIL_GENPARSER
|
2018-01-10 14:35:55 +01:00
|
|
|
bool "Generate SCONFIG & BINCFG parser using flex and bison"
|
2010-08-09 15:28:18 +02:00
|
|
|
default n
|
|
|
|
|
help
|
2012-04-12 22:00:03 +02:00
|
|
|
Enable this option if you are working on the sconfig device tree
|
2018-01-10 14:35:55 +01:00
|
|
|
parser or bincfg and made changes to the .l or .y files.
|
2012-04-12 22:00:03 +02:00
|
|
|
|
2015-02-26 20:47:19 +01:00
|
|
|
Otherwise, say N to use the provided pregenerated scanner/parser.
|
2010-08-09 15:28:18 +02:00
|
|
|
|
2010-05-19 20:41:15 +02:00
|
|
|
config USE_OPTION_TABLE
|
|
|
|
|
bool "Use CMOS for configuration values"
|
2010-07-06 23:05:04 +02:00
|
|
|
depends on HAVE_OPTION_TABLE
|
2010-05-19 20:41:15 +02:00
|
|
|
help
|
|
|
|
|
Enable this option if coreboot shall read options from the "CMOS"
|
2012-04-12 22:00:03 +02:00
|
|
|
NVRAM instead of using hard-coded values.
|
2010-05-19 20:41:15 +02:00
|
|
|
|
2015-02-14 23:15:31 +01:00
|
|
|
config STATIC_OPTION_TABLE
|
|
|
|
|
bool "Load default configuration values into CMOS on each boot"
|
|
|
|
|
depends on USE_OPTION_TABLE
|
|
|
|
|
help
|
|
|
|
|
Enable this option to reset "CMOS" NVRAM values to default on
|
|
|
|
|
every boot. Use this if you want the NVRAM configuration to
|
|
|
|
|
never be modified from its default values.
|
|
|
|
|
|
2011-05-02 21:53:04 +02:00
|
|
|
config COMPRESS_RAMSTAGE
|
|
|
|
|
bool "Compress ramstage with LZMA"
|
2019-06-08 08:59:02 +02:00
|
|
|
depends on HAVE_RAMSTAGE
|
2016-12-15 23:05:37 +01:00
|
|
|
# Default value set at the end of the file
|
2011-05-02 21:53:04 +02:00
|
|
|
help
|
|
|
|
|
Compress ramstage to save memory in the flash image. Note
|
|
|
|
|
that decompression might slow down booting if the boot flash
|
2012-04-12 22:00:03 +02:00
|
|
|
is connected through a slow link (i.e. SPI).
|
2011-05-02 21:53:04 +02:00
|
|
|
|
2015-09-29 22:51:35 +02:00
|
|
|
config COMPRESS_PRERAM_STAGES
|
|
|
|
|
bool "Compress romstage and verstage with LZ4"
|
2019-06-08 08:59:02 +02:00
|
|
|
depends on !ARCH_X86 && (HAVE_ROMSTAGE || HAVE_VERSTAGE)
|
2016-12-15 23:05:37 +01:00
|
|
|
# Default value set at the end of the file
|
2015-09-29 22:51:35 +02:00
|
|
|
help
|
|
|
|
|
Compress romstage and (if it exists) verstage with LZ4 to save flash
|
|
|
|
|
space and speed up boot, since the time for reading the image from SPI
|
|
|
|
|
(and in the vboot case verifying it) is usually much greater than the
|
|
|
|
|
time spent decompressing. Doesn't work for XIP stages (assume all
|
|
|
|
|
ARCH_X86 for now) for obvious reasons.
|
|
|
|
|
|
Introduce bootblock self-decompression
Masked ROMs are the silent killers of boot speed on devices without
memory-mapped SPI flash. They often contain awfully slow SPI drivers
(presumably bit-banged) that take hundreds of milliseconds to load our
bootblock, and every extra kilobyte of bootblock size has a hugely
disproportionate impact on boot speed. The coreboot timestamps can never
show that component, but it impacts our users all the same.
This patch tries to alleviate that issue a bit by allowing us to
compress the bootblock with LZ4, which can cut its size down to nearly
half. Of course, masked ROMs usually don't come with decompression
algorithms built in, so we need to introduce a little decompression stub
that can decompress the rest of the bootblock. This is done by creating
a new "decompressor" stage which runs before the bootblock, but includes
the compressed bootblock code in its data section. It needs to be as
small as possible to get a real benefit from this approach, which means
no device drivers, no console output, no exception handling, etc.
Besides the decompression algorithm itself we only include the timer
driver so that we can measure the boot speed impact of decompression. On
ARM and ARM64 systems, we also need to give SoC code a chance to
initialize the MMU, since running decompression without MMU is
prohibitively slow on these architectures.
This feature is implemented for ARM and ARM64 architectures for now,
although most of it is architecture-independent and it should be
relatively simple to port to other platforms where a masked ROM loads
the bootblock into SRAM. It is also supposed to be a clean starting
point from which later optimizations can hopefully cut down the
decompression stub size (currently ~4K on RK3399) a bit more.
NOTE: Bootblock compression is not for everyone. Possible side effects
include trying to run LZ4 on CPUs that come out of reset extremely
underclocked or enabling this too early in SoC bring-up and getting
frustrated trying to find issues in an undebuggable environment. Ask
your SoC vendor if bootblock compression is right for you.
Change-Id: I0dc1cad9ae7508892e477739e743cd1afb5945e8
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/26340
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
2018-05-16 23:14:04 +02:00
|
|
|
config COMPRESS_BOOTBLOCK
|
|
|
|
|
bool
|
2019-06-08 08:59:02 +02:00
|
|
|
depends on HAVE_BOOTBLOCK
|
Introduce bootblock self-decompression
Masked ROMs are the silent killers of boot speed on devices without
memory-mapped SPI flash. They often contain awfully slow SPI drivers
(presumably bit-banged) that take hundreds of milliseconds to load our
bootblock, and every extra kilobyte of bootblock size has a hugely
disproportionate impact on boot speed. The coreboot timestamps can never
show that component, but it impacts our users all the same.
This patch tries to alleviate that issue a bit by allowing us to
compress the bootblock with LZ4, which can cut its size down to nearly
half. Of course, masked ROMs usually don't come with decompression
algorithms built in, so we need to introduce a little decompression stub
that can decompress the rest of the bootblock. This is done by creating
a new "decompressor" stage which runs before the bootblock, but includes
the compressed bootblock code in its data section. It needs to be as
small as possible to get a real benefit from this approach, which means
no device drivers, no console output, no exception handling, etc.
Besides the decompression algorithm itself we only include the timer
driver so that we can measure the boot speed impact of decompression. On
ARM and ARM64 systems, we also need to give SoC code a chance to
initialize the MMU, since running decompression without MMU is
prohibitively slow on these architectures.
This feature is implemented for ARM and ARM64 architectures for now,
although most of it is architecture-independent and it should be
relatively simple to port to other platforms where a masked ROM loads
the bootblock into SRAM. It is also supposed to be a clean starting
point from which later optimizations can hopefully cut down the
decompression stub size (currently ~4K on RK3399) a bit more.
NOTE: Bootblock compression is not for everyone. Possible side effects
include trying to run LZ4 on CPUs that come out of reset extremely
underclocked or enabling this too early in SoC bring-up and getting
frustrated trying to find issues in an undebuggable environment. Ask
your SoC vendor if bootblock compression is right for you.
Change-Id: I0dc1cad9ae7508892e477739e743cd1afb5945e8
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/26340
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
2018-05-16 23:14:04 +02:00
|
|
|
help
|
|
|
|
|
This option can be used to compress the bootblock with LZ4 and attach
|
|
|
|
|
a small self-decompression stub to its front. This can drastically
|
|
|
|
|
reduce boot time on platforms where the bootblock is loaded over a
|
|
|
|
|
very slow connection and bootblock size trumps all other factors for
|
2018-09-29 17:42:52 +02:00
|
|
|
speed. Since using this option usually requires changes to the
|
Introduce bootblock self-decompression
Masked ROMs are the silent killers of boot speed on devices without
memory-mapped SPI flash. They often contain awfully slow SPI drivers
(presumably bit-banged) that take hundreds of milliseconds to load our
bootblock, and every extra kilobyte of bootblock size has a hugely
disproportionate impact on boot speed. The coreboot timestamps can never
show that component, but it impacts our users all the same.
This patch tries to alleviate that issue a bit by allowing us to
compress the bootblock with LZ4, which can cut its size down to nearly
half. Of course, masked ROMs usually don't come with decompression
algorithms built in, so we need to introduce a little decompression stub
that can decompress the rest of the bootblock. This is done by creating
a new "decompressor" stage which runs before the bootblock, but includes
the compressed bootblock code in its data section. It needs to be as
small as possible to get a real benefit from this approach, which means
no device drivers, no console output, no exception handling, etc.
Besides the decompression algorithm itself we only include the timer
driver so that we can measure the boot speed impact of decompression. On
ARM and ARM64 systems, we also need to give SoC code a chance to
initialize the MMU, since running decompression without MMU is
prohibitively slow on these architectures.
This feature is implemented for ARM and ARM64 architectures for now,
although most of it is architecture-independent and it should be
relatively simple to port to other platforms where a masked ROM loads
the bootblock into SRAM. It is also supposed to be a clean starting
point from which later optimizations can hopefully cut down the
decompression stub size (currently ~4K on RK3399) a bit more.
NOTE: Bootblock compression is not for everyone. Possible side effects
include trying to run LZ4 on CPUs that come out of reset extremely
underclocked or enabling this too early in SoC bring-up and getting
frustrated trying to find issues in an undebuggable environment. Ask
your SoC vendor if bootblock compression is right for you.
Change-Id: I0dc1cad9ae7508892e477739e743cd1afb5945e8
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://review.coreboot.org/26340
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
2018-05-16 23:14:04 +02:00
|
|
|
SoC memlayout and possibly extra support code, it should not be
|
|
|
|
|
user-selectable. (There's no real point in offering this to the user
|
|
|
|
|
anyway... if it works and saves boot time, you would always want it.)
|
|
|
|
|
|
2011-06-19 03:03:28 +02:00
|
|
|
config INCLUDE_CONFIG_FILE
|
2012-04-12 22:00:03 +02:00
|
|
|
bool "Include the coreboot .config file into the ROM image"
|
2016-12-15 23:05:37 +01:00
|
|
|
# Default value set at the end of the file
|
2012-04-12 22:00:03 +02:00
|
|
|
help
|
|
|
|
|
Include the .config file that was used to compile coreboot
|
|
|
|
|
in the (CBFS) ROM image. This is useful if you want to know which
|
|
|
|
|
options were used to build a specific coreboot.rom image.
|
|
|
|
|
|
2014-07-22 18:00:56 +02:00
|
|
|
Saying Y here will increase the image size by 2-3KB.
|
2012-04-12 22:00:03 +02:00
|
|
|
|
|
|
|
|
You can use the following command to easily list the options:
|
|
|
|
|
|
|
|
|
|
grep -a CONFIG_ coreboot.rom
|
|
|
|
|
|
|
|
|
|
Alternatively, you can also use cbfstool to print the image
|
|
|
|
|
contents (including the raw 'config' item we're looking for).
|
|
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
|
|
$ cbfstool coreboot.rom print
|
|
|
|
|
coreboot.rom: 4096 kB, bootblocksize 1008, romsize 4194304,
|
|
|
|
|
offset 0x0
|
|
|
|
|
Alignment: 64 bytes
|
2012-05-18 19:18:47 +02:00
|
|
|
|
2012-04-12 22:00:03 +02:00
|
|
|
Name Offset Type Size
|
|
|
|
|
cmos_layout.bin 0x0 cmos layout 1159
|
|
|
|
|
fallback/romstage 0x4c0 stage 339756
|
2014-07-22 18:00:56 +02:00
|
|
|
fallback/ramstage 0x53440 stage 186664
|
2012-04-12 22:00:03 +02:00
|
|
|
fallback/payload 0x80dc0 payload 51526
|
|
|
|
|
config 0x8d740 raw 3324
|
|
|
|
|
(empty) 0x8e480 null 3610440
|
2011-06-19 03:03:28 +02:00
|
|
|
|
2011-09-21 23:46:43 +02:00
|
|
|
config COLLECT_TIMESTAMPS
|
|
|
|
|
bool "Create a table of timestamps collected during boot"
|
2015-10-11 11:57:44 +02:00
|
|
|
default y if ARCH_X86
|
2011-09-21 23:46:43 +02:00
|
|
|
help
|
2012-04-12 22:00:03 +02:00
|
|
|
Make coreboot create a table of timer-ID/timer-value pairs to
|
|
|
|
|
allow measuring time spent at different phases of the boot process.
|
|
|
|
|
|
2018-03-07 23:32:16 +01:00
|
|
|
config TIMESTAMPS_ON_CONSOLE
|
|
|
|
|
bool "Print the timestamp values on the console"
|
|
|
|
|
default n
|
|
|
|
|
depends on COLLECT_TIMESTAMPS
|
|
|
|
|
help
|
|
|
|
|
Print the timestamps to the debug console if enabled at level spew.
|
|
|
|
|
|
2012-04-30 21:06:10 +02:00
|
|
|
config USE_BLOBS
|
|
|
|
|
bool "Allow use of binary-only repository"
|
|
|
|
|
help
|
|
|
|
|
This draws in the blobs repository, which contains binary files that
|
|
|
|
|
might be required for some chipsets or boards.
|
|
|
|
|
This flag ensures that a "Free" option remains available for users.
|
|
|
|
|
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
config COVERAGE
|
|
|
|
|
bool "Code coverage support"
|
|
|
|
|
depends on COMPILER_GCC
|
|
|
|
|
help
|
|
|
|
|
Add code coverage support for coreboot. This will store code
|
|
|
|
|
coverage information in CBMEM for extraction from user space.
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2017-06-12 06:07:31 +02:00
|
|
|
config UBSAN
|
|
|
|
|
bool "Undefined behavior sanitizer support"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Instrument the code with checks for undefined behavior. If unsure,
|
|
|
|
|
say N because it adds a small performance penalty and may abort
|
|
|
|
|
on code that happens to work in spite of the UB.
|
|
|
|
|
|
2018-06-03 13:55:10 +02:00
|
|
|
config NO_RELOCATABLE_RAMSTAGE
|
|
|
|
|
bool
|
|
|
|
|
default n if ARCH_X86
|
|
|
|
|
default y
|
|
|
|
|
|
2014-10-17 13:08:36 +02:00
|
|
|
config RELOCATABLE_RAMSTAGE
|
2016-06-18 06:39:31 +02:00
|
|
|
bool
|
2019-06-08 08:59:02 +02:00
|
|
|
depends on HAVE_RAMSTAGE
|
2016-06-18 06:39:31 +02:00
|
|
|
default !NO_RELOCATABLE_RAMSTAGE
|
2015-05-30 22:21:37 +02:00
|
|
|
select RELOCATABLE_MODULES
|
2014-10-17 13:08:36 +02:00
|
|
|
help
|
|
|
|
|
The reloctable ramstage support allows for the ramstage to be built
|
|
|
|
|
as a relocatable module. The stage loader can identify a place
|
|
|
|
|
out of the OS way so that copying memory is unnecessary during an S3
|
|
|
|
|
wake. When selecting this option the romstage is responsible for
|
|
|
|
|
determing a stack location to use for loading the ramstage.
|
2012-11-29 05:16:28 +01:00
|
|
|
|
2014-10-17 13:08:36 +02:00
|
|
|
config CACHE_RELOCATED_RAMSTAGE_OUTSIDE_CBMEM
|
|
|
|
|
depends on RELOCATABLE_RAMSTAGE
|
2017-01-25 15:27:52 +01:00
|
|
|
bool
|
2014-10-17 13:08:36 +02:00
|
|
|
help
|
|
|
|
|
The relocated ramstage is saved in an area specified by the
|
|
|
|
|
by the board and/or chipset.
|
2014-02-07 03:58:24 +01:00
|
|
|
|
2014-05-07 03:00:19 +02:00
|
|
|
config UPDATE_IMAGE
|
|
|
|
|
bool "Update existing coreboot.rom image"
|
|
|
|
|
help
|
|
|
|
|
If this option is enabled, no new coreboot.rom file
|
|
|
|
|
is created. Instead it is expected that there already
|
|
|
|
|
is a suitable file for further processing.
|
|
|
|
|
The bootblock will not be modified.
|
|
|
|
|
|
2016-01-20 22:59:21 +01:00
|
|
|
If unsure, select 'N'
|
|
|
|
|
|
2015-01-24 15:52:10 +01:00
|
|
|
config BOOTSPLASH_IMAGE
|
|
|
|
|
bool "Add a bootsplash image"
|
|
|
|
|
help
|
|
|
|
|
Select this option if you have a bootsplash image that you would
|
|
|
|
|
like to add to your ROM.
|
|
|
|
|
|
|
|
|
|
This will only add the image to the ROM. To actually run it check
|
|
|
|
|
options under 'Display' section.
|
|
|
|
|
|
|
|
|
|
config BOOTSPLASH_FILE
|
|
|
|
|
string "Bootsplash path and filename"
|
|
|
|
|
depends on BOOTSPLASH_IMAGE
|
2016-12-15 23:05:37 +01:00
|
|
|
# Default value set at the end of the file
|
2015-01-24 15:52:10 +01:00
|
|
|
help
|
|
|
|
|
The path and filename of the file to use as graphical bootsplash
|
|
|
|
|
screen. The file format has to be jpg.
|
|
|
|
|
|
2019-06-06 19:36:02 +02:00
|
|
|
config HAVE_RAMPAYLOAD
|
|
|
|
|
bool
|
|
|
|
|
|
2019-05-06 10:47:41 +02:00
|
|
|
config RAMPAYLOAD
|
|
|
|
|
bool "Enable coreboot flow without executing ramstage"
|
|
|
|
|
default n
|
2019-06-06 19:36:02 +02:00
|
|
|
depends on HAVE_RAMPAYLOAD
|
2019-05-06 10:47:41 +02:00
|
|
|
help
|
|
|
|
|
If this option is enabled, coreboot flow will skip ramstage
|
|
|
|
|
loading and execution of ramstage to load payload.
|
|
|
|
|
|
|
|
|
|
Instead it is expected to load payload from postcar stage itself.
|
|
|
|
|
|
|
|
|
|
In this flow coreboot will perform basic x86 initialization
|
|
|
|
|
(DRAM resource allocation), MTRR programming,
|
|
|
|
|
Skip PCI enumeration logic and only allocate BAR for fixed devices
|
|
|
|
|
(bootable devices, TPM over GSPI).
|
|
|
|
|
|
2014-10-17 13:08:36 +02:00
|
|
|
endmenu
|
|
|
|
|
|
2015-06-20 07:17:15 +02:00
|
|
|
menu "Mainboard"
|
|
|
|
|
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/mainboard/Kconfig"
|
2014-10-17 13:08:36 +02:00
|
|
|
|
2016-09-04 16:38:33 +02:00
|
|
|
config DEVICETREE
|
|
|
|
|
string
|
|
|
|
|
default "devicetree.cb"
|
|
|
|
|
help
|
|
|
|
|
This symbol allows mainboards to select a different file under their
|
|
|
|
|
mainboard directory for the devicetree.cb file. This allows the board
|
|
|
|
|
variants that need different devicetrees to be in the same directory.
|
|
|
|
|
|
|
|
|
|
Examples: "devicetree.variant.cb"
|
|
|
|
|
"variant/devicetree.cb"
|
|
|
|
|
|
2018-06-22 03:50:48 +02:00
|
|
|
config OVERRIDE_DEVICETREE
|
|
|
|
|
string
|
|
|
|
|
default ""
|
|
|
|
|
help
|
|
|
|
|
This symbol allows variants to provide an override devicetree file to
|
|
|
|
|
override the registers and/or add new devices on top of the ones
|
|
|
|
|
provided by baseboard devicetree using CONFIG_DEVICETREE.
|
|
|
|
|
|
|
|
|
|
Examples: "devicetree.variant-override.cb"
|
|
|
|
|
"variant/devicetree-override.cb"
|
|
|
|
|
|
2015-06-20 07:17:15 +02:00
|
|
|
config CBFS_SIZE
|
|
|
|
|
hex "Size of CBFS filesystem in ROM"
|
2016-12-15 23:05:37 +01:00
|
|
|
# Default value set at the end of the file
|
2015-06-20 07:17:15 +02:00
|
|
|
help
|
|
|
|
|
This is the part of the ROM actually managed by CBFS, located at the
|
|
|
|
|
end of the ROM (passed through cbfstool -o) on x86 and at at the start
|
|
|
|
|
of the ROM (passed through cbfstool -s) everywhere else. It defaults
|
|
|
|
|
to span the whole ROM on all but Intel systems that use an Intel Firmware
|
|
|
|
|
Descriptor. It can be overridden to make coreboot live alongside other
|
|
|
|
|
components like ChromeOS's vboot/FMAP or Intel's IFD / ME / TXE
|
|
|
|
|
binaries.
|
|
|
|
|
|
2015-09-16 18:10:52 +02:00
|
|
|
config FMDFILE
|
|
|
|
|
string "fmap description file in fmd format"
|
2015-12-12 00:23:15 +01:00
|
|
|
default "src/mainboard/$(CONFIG_MAINBOARD_DIR)/chromeos.fmd" if CHROMEOS
|
2015-09-16 18:10:52 +02:00
|
|
|
default ""
|
|
|
|
|
help
|
|
|
|
|
The build system creates a default FMAP from ROM_SIZE and CBFS_SIZE,
|
|
|
|
|
but in some cases more complex setups are required.
|
|
|
|
|
When an fmd is specified, it overrides the default format.
|
|
|
|
|
|
2015-12-27 00:51:16 +01:00
|
|
|
endmenu
|
|
|
|
|
|
2016-01-25 03:38:33 +01:00
|
|
|
# load site-local kconfig to allow user specific defaults and overrides
|
|
|
|
|
source "site-local/Kconfig"
|
|
|
|
|
|
2014-10-17 13:08:36 +02:00
|
|
|
config SYSTEM_TYPE_LAPTOP
|
2015-04-27 02:53:26 +02:00
|
|
|
default n
|
|
|
|
|
bool
|
2014-10-17 13:08:36 +02:00
|
|
|
|
2019-02-01 20:33:57 +01:00
|
|
|
config SYSTEM_TYPE_TABLET
|
|
|
|
|
default n
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config SYSTEM_TYPE_DETACHABLE
|
|
|
|
|
default n
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config SYSTEM_TYPE_CONVERTIBLE
|
|
|
|
|
default n
|
|
|
|
|
bool
|
|
|
|
|
|
2016-01-14 15:08:36 +01:00
|
|
|
config CBFS_AUTOGEN_ATTRIBUTES
|
|
|
|
|
default n
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
If this option is selected, every file in cbfs which has a constraint
|
|
|
|
|
regarding position or alignment will get an additional file attribute
|
|
|
|
|
which describes this constraint.
|
|
|
|
|
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
menu "Chipset"
|
|
|
|
|
|
2015-06-09 03:11:56 +02:00
|
|
|
comment "SoC"
|
2017-10-20 18:43:39 +02:00
|
|
|
source "src/soc/*/Kconfig"
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
comment "CPU"
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/cpu/Kconfig"
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
comment "Northbridge"
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/northbridge/*/*/Kconfig"
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
comment "Southbridge"
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/southbridge/*/*/Kconfig"
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
comment "Super I/O"
|
2016-07-29 23:31:45 +02:00
|
|
|
source "src/superio/*/*/Kconfig"
|
2011-01-27 12:43:03 +01:00
|
|
|
comment "Embedded Controllers"
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/ec/acpi/Kconfig"
|
|
|
|
|
source "src/ec/*/*/Kconfig"
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
|
2015-06-21 00:17:12 +02:00
|
|
|
source "src/southbridge/intel/common/firmware/Kconfig"
|
2015-06-20 06:30:43 +02:00
|
|
|
source "src/vendorcode/*/Kconfig"
|
2015-06-21 00:17:12 +02:00
|
|
|
|
2015-06-20 06:30:43 +02:00
|
|
|
source "src/arch/*/Kconfig"
|
|
|
|
|
|
Add kconfig menus for most chipset VIDEO_MB values.
VIDEO_MB is a variable that defines how many MB of RAM will be used
for onboard graphics frame buffer. It's northbridge-dependent which
values for CONFIG_MB are valid (but not board-dependent).
This patch adds choices for menuconfig to select the VIDEO_MB value for:
- Intel 82810
- Intel 82830
- VIA CN400
- VIA CN700
Note: CN400 and CN700 are based on the CX700 datasheet, not sure if they're
correct. If somebody has CN400 and CN700 datasheets, please verify.
We drop all per-board VIDEO_MB variables in per-board Kconfig files as
there's a northbridge-specific option/default now (plus the user can override
the value if needed in menuconfig).
As CONFIG_MB is chipset-specific but not board-specific (and never was), filter
it in util/compareboard/compareboard, we don't need to match those values.
Finally, put "CPU", "Northbridge", "Southbridge", "Super I/O", and
"Devices" sections into the "Chipset" menu, where NB-specific
options will appear if you select a board using a certain NB,
SB-specific options would appear in the "Southbridge" section etc.
Signed-off-by: Uwe Hermann <uwe@hermann-uwe.de>
Acked-by: Myles Watson <mylesgw@gmail.com>
git-svn-id: svn://svn.coreboot.org/coreboot/trunk@4866 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1
2009-10-26 22:42:13 +01:00
|
|
|
endmenu
|
2009-08-12 17:00:51 +02:00
|
|
|
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/device/Kconfig"
|
2012-11-14 02:00:01 +01:00
|
|
|
|
2010-05-16 17:31:53 +02:00
|
|
|
menu "Generic Drivers"
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/drivers/*/Kconfig"
|
2016-03-12 05:22:28 +01:00
|
|
|
source "src/drivers/*/*/Kconfig"
|
2017-05-09 01:56:03 +02:00
|
|
|
source "src/commonlib/storage/Kconfig"
|
2010-05-16 17:31:53 +02:00
|
|
|
endmenu
|
|
|
|
|
|
2017-10-16 17:09:33 +02:00
|
|
|
menu "Security"
|
|
|
|
|
|
|
|
|
|
source "src/security/Kconfig"
|
|
|
|
|
|
|
|
|
|
endmenu
|
|
|
|
|
|
2016-05-17 19:28:23 +02:00
|
|
|
source "src/acpi/Kconfig"
|
|
|
|
|
|
2016-08-11 18:02:26 +02:00
|
|
|
# This option is for the current boards/chipsets where SPI flash
|
|
|
|
|
# is not the boot device. Currently nearly all boards/chipsets assume
|
|
|
|
|
# SPI flash is the boot device.
|
|
|
|
|
config BOOT_DEVICE_NOT_SPI_FLASH
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config BOOT_DEVICE_SPI_FLASH
|
|
|
|
|
bool
|
|
|
|
|
default y if !BOOT_DEVICE_NOT_SPI_FLASH
|
|
|
|
|
default n
|
|
|
|
|
|
2016-08-11 21:04:10 +02:00
|
|
|
config BOOT_DEVICE_MEMORY_MAPPED
|
|
|
|
|
bool
|
|
|
|
|
default y if ARCH_X86 && BOOT_DEVICE_SPI_FLASH
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Inform system if SPI is memory-mapped or not.
|
|
|
|
|
|
2016-08-12 22:00:10 +02:00
|
|
|
config BOOT_DEVICE_SUPPORTS_WRITES
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Indicate that the platform has writable boot device
|
|
|
|
|
support.
|
|
|
|
|
|
2015-04-22 13:28:21 +02:00
|
|
|
config RTC
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2009-08-12 17:00:51 +02:00
|
|
|
config HEAP_SIZE
|
|
|
|
|
hex
|
2019-04-23 03:46:27 +02:00
|
|
|
default 0x100000 if FLATTENED_DEVICE_TREE
|
2009-10-16 21:12:49 +02:00
|
|
|
default 0x4000
|
2009-08-12 17:00:51 +02:00
|
|
|
|
2014-09-19 22:18:16 +02:00
|
|
|
config STACK_SIZE
|
|
|
|
|
hex
|
2015-10-13 01:45:21 +02:00
|
|
|
default 0x1000 if ARCH_X86
|
|
|
|
|
default 0x0
|
2014-09-19 22:18:16 +02:00
|
|
|
|
2009-08-12 17:00:51 +02:00
|
|
|
config MAX_CPUS
|
|
|
|
|
int
|
|
|
|
|
default 1
|
|
|
|
|
|
2015-04-04 01:58:28 +02:00
|
|
|
source "src/console/Kconfig"
|
2009-08-12 17:00:51 +02:00
|
|
|
|
|
|
|
|
config HAVE_ACPI_RESUME
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2016-06-28 06:38:46 +02:00
|
|
|
config ACPI_HUGE_LOWMEM_BACKUP
|
|
|
|
|
bool
|
2016-11-10 10:50:21 +01:00
|
|
|
default n
|
2016-06-28 06:38:46 +02:00
|
|
|
help
|
|
|
|
|
On S3 resume path, backup low memory from RAMBASE..RAMTOP in CBMEM.
|
|
|
|
|
|
2016-01-22 22:26:04 +01:00
|
|
|
config RESUME_PATH_SAME_AS_BOOT
|
|
|
|
|
bool
|
|
|
|
|
default y if ARCH_X86
|
|
|
|
|
depends on HAVE_ACPI_RESUME
|
|
|
|
|
help
|
|
|
|
|
This option indicates that when a system resumes it takes the
|
|
|
|
|
same path as a regular boot. e.g. an x86 system runs from the
|
|
|
|
|
reset vector at 0xfffffff0 on both resume and warm/cold boot.
|
|
|
|
|
|
2015-05-18 23:04:10 +02:00
|
|
|
config HAVE_ROMSTAGE_CONSOLE_SPINLOCK
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2015-08-29 02:52:05 +02:00
|
|
|
config HAVE_ROMSTAGE_NVRAM_CBFS_SPINLOCK
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This should be enabled on certain plaforms, such as the AMD
|
|
|
|
|
SR565x, that cannot handle concurrent CBFS accesses from
|
|
|
|
|
multiple APs during early startup.
|
|
|
|
|
|
2015-08-29 03:48:17 +02:00
|
|
|
config HAVE_ROMSTAGE_MICROCODE_CBFS_SPINLOCK
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2013-04-30 05:31:51 +02:00
|
|
|
config HAVE_MONOTONIC_TIMER
|
|
|
|
|
def_bool n
|
|
|
|
|
help
|
|
|
|
|
The board/chipset provides a monotonic timer.
|
|
|
|
|
|
2014-09-25 17:05:15 +02:00
|
|
|
config GENERIC_UDELAY
|
|
|
|
|
def_bool n
|
|
|
|
|
depends on HAVE_MONOTONIC_TIMER
|
|
|
|
|
help
|
|
|
|
|
The board/chipset uses a generic udelay function utilizing the
|
|
|
|
|
monotonic timer.
|
|
|
|
|
|
2013-04-30 16:58:12 +02:00
|
|
|
config TIMER_QUEUE
|
|
|
|
|
def_bool n
|
|
|
|
|
depends on HAVE_MONOTONIC_TIMER
|
|
|
|
|
help
|
2013-09-13 06:57:49 +02:00
|
|
|
Provide a timer queue for performing time-based callbacks.
|
2013-04-30 16:58:12 +02:00
|
|
|
|
2013-05-06 19:20:52 +02:00
|
|
|
config COOP_MULTITASKING
|
|
|
|
|
def_bool n
|
2013-05-06 19:22:23 +02:00
|
|
|
depends on TIMER_QUEUE && ARCH_X86
|
2013-05-06 19:20:52 +02:00
|
|
|
help
|
|
|
|
|
Cooperative multitasking allows callbacks to be multiplexed on the
|
|
|
|
|
main thread of ramstage. With this enabled it allows for multiple
|
|
|
|
|
execution paths to take place when they have udelay() calls within
|
|
|
|
|
their code.
|
|
|
|
|
|
|
|
|
|
config NUM_THREADS
|
|
|
|
|
int
|
|
|
|
|
default 4
|
|
|
|
|
depends on COOP_MULTITASKING
|
|
|
|
|
help
|
|
|
|
|
How many execution threads to cooperatively multitask with.
|
|
|
|
|
|
2009-08-12 17:00:51 +02:00
|
|
|
config HAVE_OPTION_TABLE
|
|
|
|
|
bool
|
2010-07-06 23:05:04 +02:00
|
|
|
default n
|
2009-10-15 19:49:07 +02:00
|
|
|
help
|
|
|
|
|
This variable specifies whether a given board has a cmos.layout
|
|
|
|
|
file containing NVRAM/CMOS bit definitions.
|
2010-07-06 23:05:04 +02:00
|
|
|
It defaults to 'n' but can be selected in mainboard/*/Kconfig.
|
2009-08-12 17:00:51 +02:00
|
|
|
|
|
|
|
|
config PIRQ_ROUTE
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config HAVE_SMI_HANDLER
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config PCI_IO_CFG_EXT
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config IOAPIC
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2009-09-22 20:49:08 +02:00
|
|
|
config USE_WATCHDOG_ON_BOOT
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
|
|
|
|
config GFXUMA
|
|
|
|
|
bool
|
2009-10-26 16:14:07 +01:00
|
|
|
default n
|
2009-09-22 20:49:08 +02:00
|
|
|
help
|
|
|
|
|
Enable Unified Memory Architecture for graphics.
|
|
|
|
|
|
2009-10-15 15:35:47 +02:00
|
|
|
config HAVE_ACPI_TABLES
|
|
|
|
|
bool
|
2009-10-15 19:49:07 +02:00
|
|
|
help
|
|
|
|
|
This variable specifies whether a given board has ACPI table support.
|
|
|
|
|
It is usually set in mainboard/*/Kconfig.
|
2009-10-15 15:35:47 +02:00
|
|
|
|
|
|
|
|
config HAVE_MP_TABLE
|
|
|
|
|
bool
|
2009-10-15 19:49:07 +02:00
|
|
|
help
|
|
|
|
|
This variable specifies whether a given board has MP table support.
|
|
|
|
|
It is usually set in mainboard/*/Kconfig.
|
|
|
|
|
Whether or not the MP table is actually generated by coreboot
|
|
|
|
|
is configurable by the user via GENERATE_MP_TABLE.
|
2009-10-15 15:35:47 +02:00
|
|
|
|
|
|
|
|
config HAVE_PIRQ_TABLE
|
|
|
|
|
bool
|
2009-10-15 19:49:07 +02:00
|
|
|
help
|
|
|
|
|
This variable specifies whether a given board has PIRQ table support.
|
|
|
|
|
It is usually set in mainboard/*/Kconfig.
|
|
|
|
|
Whether or not the PIRQ table is actually generated by coreboot
|
|
|
|
|
is configurable by the user via GENERATE_PIRQ_TABLE.
|
2009-10-15 15:35:47 +02:00
|
|
|
|
2012-08-23 09:32:58 +02:00
|
|
|
config MAX_PIRQ_LINKS
|
|
|
|
|
int
|
|
|
|
|
default 4
|
|
|
|
|
help
|
|
|
|
|
This variable specifies the number of PIRQ interrupt links which are
|
|
|
|
|
routable. On most chipsets, this is 4, INTA through INTD. Some
|
|
|
|
|
chipsets offer more than four links, commonly up to INTH. They may
|
|
|
|
|
also have a separate link for ATA or IOAPIC interrupts. When the PIRQ
|
|
|
|
|
table specifies links greater than 4, pirq_route_irqs will not
|
|
|
|
|
function properly, unless this variable is correctly set.
|
|
|
|
|
|
2014-10-16 12:48:19 +02:00
|
|
|
config COMMON_FADT
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2015-11-17 23:31:00 +01:00
|
|
|
config ACPI_NHLT
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Build support for NHLT (non HD Audio) ACPI table generation.
|
|
|
|
|
|
2018-09-04 20:32:56 +02:00
|
|
|
config ACPI_BERT
|
|
|
|
|
bool
|
|
|
|
|
depends on HAVE_ACPI_TABLES
|
|
|
|
|
help
|
|
|
|
|
Build an ACPI Boot Error Record Table.
|
|
|
|
|
|
2009-10-26 16:14:07 +01:00
|
|
|
#These Options are here to avoid "undefined" warnings.
|
|
|
|
|
#The actual selection and help texts are in the following menu.
|
|
|
|
|
|
|
|
|
|
menu "System tables"
|
2009-09-22 20:49:08 +02:00
|
|
|
|
2009-10-15 15:35:47 +02:00
|
|
|
config GENERATE_MP_TABLE
|
2012-11-14 02:33:08 +01:00
|
|
|
prompt "Generate an MP table" if HAVE_MP_TABLE || DRIVERS_GENERIC_IOAPIC
|
|
|
|
|
bool
|
|
|
|
|
default HAVE_MP_TABLE || DRIVERS_GENERIC_IOAPIC
|
2009-10-15 19:49:07 +02:00
|
|
|
help
|
|
|
|
|
Generate an MP table (conforming to the Intel MultiProcessor
|
|
|
|
|
specification 1.4) for this board.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2009-09-22 20:49:08 +02:00
|
|
|
|
2009-10-15 15:35:47 +02:00
|
|
|
config GENERATE_PIRQ_TABLE
|
2012-11-14 02:33:08 +01:00
|
|
|
prompt "Generate a PIRQ table" if HAVE_PIRQ_TABLE
|
|
|
|
|
bool
|
|
|
|
|
default HAVE_PIRQ_TABLE
|
2009-10-15 19:49:07 +02:00
|
|
|
help
|
|
|
|
|
Generate a PIRQ table for this board.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
2009-09-22 20:49:08 +02:00
|
|
|
|
2011-08-14 20:56:34 +02:00
|
|
|
config GENERATE_SMBIOS_TABLES
|
|
|
|
|
depends on ARCH_X86
|
|
|
|
|
bool "Generate SMBIOS tables"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Generate SMBIOS tables for this board.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2015-05-30 23:08:26 +02:00
|
|
|
config SMBIOS_PROVIDED_BY_MOBO
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
|
2014-10-17 13:28:15 +02:00
|
|
|
config MAINBOARD_SERIAL_NUMBER
|
2017-11-01 09:49:16 +01:00
|
|
|
prompt "SMBIOS Serial Number" if !SMBIOS_PROVIDED_BY_MOBO
|
|
|
|
|
string
|
2014-10-17 13:28:15 +02:00
|
|
|
depends on GENERATE_SMBIOS_TABLES
|
|
|
|
|
default "123456789"
|
2015-04-27 02:53:26 +02:00
|
|
|
help
|
2014-10-17 13:28:15 +02:00
|
|
|
The Serial Number to store in SMBIOS structures.
|
|
|
|
|
|
|
|
|
|
config MAINBOARD_VERSION
|
2017-11-01 09:49:16 +01:00
|
|
|
prompt "SMBIOS Version Number" if !SMBIOS_PROVIDED_BY_MOBO
|
|
|
|
|
string
|
2014-10-17 13:28:15 +02:00
|
|
|
depends on GENERATE_SMBIOS_TABLES
|
|
|
|
|
default "1.0"
|
|
|
|
|
help
|
|
|
|
|
The Version Number to store in SMBIOS structures.
|
|
|
|
|
|
|
|
|
|
config MAINBOARD_SMBIOS_MANUFACTURER
|
2017-11-01 09:49:16 +01:00
|
|
|
prompt "SMBIOS Manufacturer" if !SMBIOS_PROVIDED_BY_MOBO
|
|
|
|
|
string
|
2014-10-17 13:28:15 +02:00
|
|
|
depends on GENERATE_SMBIOS_TABLES
|
|
|
|
|
default MAINBOARD_VENDOR
|
|
|
|
|
help
|
|
|
|
|
Override the default Manufacturer stored in SMBIOS structures.
|
|
|
|
|
|
|
|
|
|
config MAINBOARD_SMBIOS_PRODUCT_NAME
|
2017-11-01 09:49:16 +01:00
|
|
|
prompt "SMBIOS Product name" if !SMBIOS_PROVIDED_BY_MOBO
|
|
|
|
|
string
|
2014-10-17 13:28:15 +02:00
|
|
|
depends on GENERATE_SMBIOS_TABLES
|
|
|
|
|
default MAINBOARD_PART_NUMBER
|
|
|
|
|
help
|
|
|
|
|
Override the default Product name stored in SMBIOS structures.
|
|
|
|
|
|
2018-02-28 13:39:55 +01:00
|
|
|
config SMBIOS_ENCLOSURE_TYPE
|
|
|
|
|
hex
|
|
|
|
|
depends on GENERATE_SMBIOS_TABLES
|
|
|
|
|
default 0x09 if SYSTEM_TYPE_LAPTOP
|
2019-02-01 20:33:57 +01:00
|
|
|
default 0x1e if SYSTEM_TYPE_TABLET
|
|
|
|
|
default 0x1f if SYSTEM_TYPE_CONVERTIBLE
|
|
|
|
|
default 0x20 if SYSTEM_TYPE_DETACHABLE
|
2018-02-28 13:39:55 +01:00
|
|
|
default 0x03
|
|
|
|
|
help
|
|
|
|
|
System Enclosure or Chassis Types as defined in SMBIOS specification.
|
2019-02-01 20:33:57 +01:00
|
|
|
The default value is SMBIOS_ENCLOSURE_DESKTOP (0x03) but laptop,
|
|
|
|
|
convertible, or tablet enclosure will be used if the appropriate
|
|
|
|
|
system type is selected.
|
2018-02-28 13:39:55 +01:00
|
|
|
|
2009-09-22 20:49:08 +02:00
|
|
|
endmenu
|
|
|
|
|
|
2016-02-05 03:52:27 +01:00
|
|
|
source "payloads/Kconfig"
|
2009-09-17 18:21:31 +02:00
|
|
|
|
2009-10-07 18:15:40 +02:00
|
|
|
menu "Debugging"
|
|
|
|
|
|
2018-11-13 19:28:07 +01:00
|
|
|
comment "CPU Debug Settings"
|
|
|
|
|
source "src/cpu/*/Kconfig.debug"
|
|
|
|
|
|
|
|
|
|
comment "General Debug Settings"
|
|
|
|
|
|
2009-10-07 18:15:40 +02:00
|
|
|
# TODO: Better help text and detailed instructions.
|
2009-08-12 17:00:51 +02:00
|
|
|
config GDB_STUB
|
2009-08-25 02:53:22 +02:00
|
|
|
bool "GDB debugging support"
|
2012-03-25 20:51:16 +02:00
|
|
|
default n
|
2015-12-10 22:04:56 +01:00
|
|
|
depends on CONSOLE_SERIAL
|
2009-08-12 17:00:51 +02:00
|
|
|
help
|
2009-08-25 02:53:22 +02:00
|
|
|
If enabled, you will be able to set breakpoints for gdb debugging.
|
2010-12-11 21:33:41 +01:00
|
|
|
See src/arch/x86/lib/c_start.S for details.
|
2009-08-12 17:00:51 +02:00
|
|
|
|
2012-06-22 15:56:37 +02:00
|
|
|
config GDB_WAIT
|
2015-12-10 21:58:52 +01:00
|
|
|
bool "Wait for a GDB connection in the ramstage"
|
2012-06-22 15:56:37 +02:00
|
|
|
default n
|
|
|
|
|
depends on GDB_STUB
|
|
|
|
|
help
|
2015-12-10 21:58:52 +01:00
|
|
|
If enabled, coreboot will wait for a GDB connection in the ramstage.
|
|
|
|
|
|
2012-06-22 15:56:37 +02:00
|
|
|
|
2015-02-18 02:27:23 +01:00
|
|
|
config FATAL_ASSERTS
|
|
|
|
|
bool "Halt when hitting a BUG() or assertion error"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If enabled, coreboot will call hlt() on a BUG() or failed ASSERT().
|
|
|
|
|
|
2018-11-13 22:06:40 +01:00
|
|
|
config HAVE_DEBUG_GPIO
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config DEBUG_GPIO
|
|
|
|
|
bool "Output verbose GPIO debug messages"
|
|
|
|
|
depends on HAVE_DEBUG_GPIO
|
|
|
|
|
|
2012-05-03 01:33:18 +02:00
|
|
|
config DEBUG_CBFS
|
|
|
|
|
bool "Output verbose CBFS debug messages"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option enables additional CBFS related debug messages.
|
|
|
|
|
|
2010-08-26 14:46:02 +02:00
|
|
|
config HAVE_DEBUG_RAM_SETUP
|
|
|
|
|
def_bool n
|
|
|
|
|
|
2010-03-05 11:03:50 +01:00
|
|
|
config DEBUG_RAM_SETUP
|
|
|
|
|
bool "Output verbose RAM init debug messages"
|
|
|
|
|
default n
|
2010-08-26 14:46:02 +02:00
|
|
|
depends on HAVE_DEBUG_RAM_SETUP
|
2010-03-05 11:03:50 +01:00
|
|
|
help
|
|
|
|
|
This option enables additional RAM init related debug messages.
|
|
|
|
|
It is recommended to enable this when debugging issues on your
|
|
|
|
|
board which might be RAM init related.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-06-01 21:25:31 +02:00
|
|
|
config DEBUG_PIRQ
|
|
|
|
|
bool "Check PIRQ table consistency"
|
|
|
|
|
default n
|
|
|
|
|
depends on GENERATE_PIRQ_TABLE
|
|
|
|
|
help
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-08-26 14:46:02 +02:00
|
|
|
config HAVE_DEBUG_SMBUS
|
|
|
|
|
def_bool n
|
|
|
|
|
|
2010-03-05 11:03:50 +01:00
|
|
|
config DEBUG_SMBUS
|
|
|
|
|
bool "Output verbose SMBus debug messages"
|
|
|
|
|
default n
|
2010-08-26 14:46:02 +02:00
|
|
|
depends on HAVE_DEBUG_SMBUS
|
2010-03-05 11:03:50 +01:00
|
|
|
help
|
|
|
|
|
This option enables additional SMBus (and SPD) debug messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config DEBUG_SMI
|
|
|
|
|
bool "Output verbose SMI debug messages"
|
|
|
|
|
default n
|
|
|
|
|
depends on HAVE_SMI_HANDLER
|
2018-06-05 22:34:08 +02:00
|
|
|
select SPI_FLASH_SMM if SPI_CONSOLE || CONSOLE_SPI_FLASH
|
2010-03-05 11:03:50 +01:00
|
|
|
help
|
|
|
|
|
This option enables additional SMI related debug messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-11-10 01:14:32 +01:00
|
|
|
# Only visible if debug level is DEBUG (7) or SPEW (8) as it does additional
|
|
|
|
|
# printk(BIOS_DEBUG, ...) calls.
|
|
|
|
|
config DEBUG_MALLOC
|
2012-11-14 02:00:01 +01:00
|
|
|
prompt "Output verbose malloc debug messages" if DEFAULT_CONSOLE_LOGLEVEL_7 || DEFAULT_CONSOLE_LOGLEVEL_8
|
|
|
|
|
bool
|
2010-11-10 01:14:32 +01:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option enables additional malloc related debug messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2011-07-01 23:44:39 +02:00
|
|
|
|
|
|
|
|
# Only visible if debug level is DEBUG (7) or SPEW (8) as it does additional
|
|
|
|
|
# printk(BIOS_DEBUG, ...) calls.
|
|
|
|
|
config DEBUG_ACPI
|
2012-11-14 02:00:01 +01:00
|
|
|
prompt "Output verbose ACPI debug messages" if DEFAULT_CONSOLE_LOGLEVEL_7 || DEFAULT_CONSOLE_LOGLEVEL_8
|
|
|
|
|
bool
|
2011-07-01 23:44:39 +02:00
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option enables additional ACPI related debug messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will slightly increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2010-11-10 01:14:32 +01:00
|
|
|
|
2018-12-31 14:22:34 +01:00
|
|
|
config DEBUG_CONSOLE_INIT
|
|
|
|
|
bool "Debug console initialisation code"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
With this option printk()'s are attempted before console hardware
|
|
|
|
|
initialisation has been completed. Your mileage may vary.
|
|
|
|
|
|
|
|
|
|
Typically you will need to modify source in console_hw_init() such
|
|
|
|
|
that a working console appears before the one you want to debug.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-11-10 01:14:32 +01:00
|
|
|
# Only visible if debug level is DEBUG (7) or SPEW (8) as it does additional
|
|
|
|
|
# printk(BIOS_DEBUG, ...) calls.
|
2010-09-08 00:30:15 +02:00
|
|
|
config REALMODE_DEBUG
|
2012-11-14 02:00:01 +01:00
|
|
|
prompt "Enable debug messages for option ROM execution" if DEFAULT_CONSOLE_LOGLEVEL_7 || DEFAULT_CONSOLE_LOGLEVEL_8
|
|
|
|
|
bool
|
2010-09-08 00:30:15 +02:00
|
|
|
default n
|
2010-11-10 03:00:32 +01:00
|
|
|
depends on PCI_OPTION_ROM_RUN_REALMODE
|
2010-09-08 00:30:15 +02:00
|
|
|
help
|
|
|
|
|
This option enables additional x86emu related debug messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the time to emulate a ROM.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2010-03-05 11:03:50 +01:00
|
|
|
config X86EMU_DEBUG
|
|
|
|
|
bool "Output verbose x86emu debug messages"
|
|
|
|
|
default n
|
|
|
|
|
depends on PCI_OPTION_ROM_RUN_YABEL
|
|
|
|
|
help
|
|
|
|
|
This option enables additional x86emu related debug messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_JMP
|
|
|
|
|
bool "Trace JMP/RETF"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print information about JMP and RETF opcodes from x86emu.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_TRACE
|
|
|
|
|
bool "Trace all opcodes"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print _all_ opcodes that are executed by x86emu.
|
2010-04-27 08:56:47 +02:00
|
|
|
|
2010-03-05 11:03:50 +01:00
|
|
|
WARNING: This will produce a LOT of output and take a long time.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_PNP
|
|
|
|
|
bool "Log Plug&Play accesses"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print Plug And Play accesses made by option ROMs.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_DISK
|
|
|
|
|
bool "Log Disk I/O"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print Disk I/O related messages.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_PMM
|
|
|
|
|
bool "Log PMM"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print messages related to POST Memory Manager (PMM).
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_VBE
|
|
|
|
|
bool "Debug VESA BIOS Extensions"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print messages related to VESA BIOS Extension (VBE) functions.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_INT10
|
|
|
|
|
bool "Redirect INT10 output to console"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Let INT10 (i.e. character output) calls print messages to debug output.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_INTERRUPTS
|
|
|
|
|
bool "Log intXX calls"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print messages related to interrupt handling.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_CHECK_VMEM_ACCESS
|
|
|
|
|
bool "Log special memory accesses"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print messages related to accesses to certain areas of the virtual
|
|
|
|
|
memory (e.g. BDA (BIOS Data Area) or interrupt vectors)
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_MEM
|
|
|
|
|
bool "Log all memory accesses"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print memory accesses made by option ROM.
|
|
|
|
|
Note: This also includes accesses to fetch instructions.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config X86EMU_DEBUG_IO
|
|
|
|
|
bool "Log IO accesses"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG
|
|
|
|
|
help
|
|
|
|
|
Print I/O accesses made by option ROM.
|
|
|
|
|
|
|
|
|
|
Note: This option will increase the size of the coreboot image.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-05-15 00:19:49 +02:00
|
|
|
config X86EMU_DEBUG_TIMINGS
|
|
|
|
|
bool "Output timing information"
|
|
|
|
|
default n
|
|
|
|
|
depends on X86EMU_DEBUG && UDELAY_LAPIC && HAVE_MONOTONIC_TIMER
|
|
|
|
|
help
|
|
|
|
|
Print timing information needed by i915tool.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2012-05-10 20:27:32 +02:00
|
|
|
config DEBUG_SPI_FLASH
|
|
|
|
|
bool "Output verbose SPI flash debug messages"
|
|
|
|
|
default n
|
|
|
|
|
depends on SPI_FLASH
|
|
|
|
|
help
|
|
|
|
|
This option enables additional SPI flash related debug messages.
|
|
|
|
|
|
2012-04-04 00:07:22 +02:00
|
|
|
if SOUTHBRIDGE_INTEL_BD82X6X && DEFAULT_CONSOLE_LOGLEVEL_8
|
|
|
|
|
# Only visible with the right southbridge and loglevel.
|
|
|
|
|
config DEBUG_INTEL_ME
|
|
|
|
|
bool "Verbose logging for Intel Management Engine"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Enable verbose logging for Intel Management Engine driver that
|
|
|
|
|
is present on Intel 6-series chipsets.
|
|
|
|
|
endif
|
|
|
|
|
|
2011-09-02 23:23:41 +02:00
|
|
|
config TRACE
|
|
|
|
|
bool "Trace function calls"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
If enabled, every function will print information to console once
|
|
|
|
|
the function is entered. The syntax is ~0xaaaabbbb(0xccccdddd)
|
|
|
|
|
the 0xaaaabbbb is the actual function and 0xccccdddd is EIP
|
2015-11-18 17:46:53 +01:00
|
|
|
of calling function. Please note some printk related functions
|
2011-09-02 23:23:41 +02:00
|
|
|
are omitted from trace to have good looking console dumps.
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
|
|
|
|
|
config DEBUG_COVERAGE
|
|
|
|
|
bool "Debug code coverage"
|
|
|
|
|
default n
|
|
|
|
|
depends on COVERAGE
|
|
|
|
|
help
|
|
|
|
|
If enabled, the code coverage hooks in coreboot will output some
|
|
|
|
|
information about the coverage data that is dumped.
|
|
|
|
|
|
2016-06-29 21:59:32 +02:00
|
|
|
config DEBUG_BOOT_STATE
|
|
|
|
|
bool "Debug boot state machine"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Control debugging of the boot state machine. When selected displays
|
|
|
|
|
the state boundaries in ramstage.
|
|
|
|
|
|
2016-10-05 17:43:56 +02:00
|
|
|
config DEBUG_ADA_CODE
|
|
|
|
|
bool "Compile debug code in Ada sources"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Add the compiler switch `-gnata` to compile code guarded by
|
|
|
|
|
`pragma Debug`.
|
|
|
|
|
|
2018-07-12 23:26:07 +02:00
|
|
|
config HAVE_EM100_SUPPORT
|
|
|
|
|
bool "Platform can support the Dediprog EM100 SPI emulator"
|
|
|
|
|
help
|
|
|
|
|
This is enabled by platforms which can support using the EM100.
|
|
|
|
|
|
|
|
|
|
config EM100
|
|
|
|
|
bool "Configure image for EM100 usage"
|
|
|
|
|
depends on HAVE_EM100_SUPPORT
|
|
|
|
|
help
|
|
|
|
|
The Dediprog EM100 SPI emulator allows fast loading of new SPI images
|
|
|
|
|
over USB. However it only supports a maximum SPI clock of 20MHz and
|
|
|
|
|
single data output. Enable this option to use a 20MHz SPI clock and
|
|
|
|
|
disable "Dual Output Fast Read" Support.
|
|
|
|
|
|
|
|
|
|
On AMD platforms this changes the SPI speed at run-time if the
|
|
|
|
|
mainboard code supports this. On supported Intel platforms this works
|
|
|
|
|
by changing the settings in the descriptor.bin file.
|
|
|
|
|
|
2009-10-07 18:15:40 +02:00
|
|
|
endmenu
|
|
|
|
|
|
2016-12-15 23:25:15 +01:00
|
|
|
|
|
|
|
|
###############################################################################
|
|
|
|
|
# Set variables with no prompt - these can be set anywhere, and putting at
|
|
|
|
|
# the end of this file gives the most flexibility.
|
2017-05-18 18:07:34 +02:00
|
|
|
|
|
|
|
|
source "src/lib/Kconfig"
|
|
|
|
|
|
2009-10-26 16:14:07 +01:00
|
|
|
config ENABLE_APIC_EXT_ID
|
|
|
|
|
bool
|
|
|
|
|
default n
|
2009-11-12 17:38:03 +01:00
|
|
|
|
|
|
|
|
config WARNINGS_ARE_ERRORS
|
|
|
|
|
bool
|
2014-11-17 17:17:54 +01:00
|
|
|
default y
|
2009-11-27 17:55:13 +01:00
|
|
|
|
2010-10-13 08:23:02 +02:00
|
|
|
# The four POWER_BUTTON_DEFAULT_ENABLE, POWER_BUTTON_DEFAULT_DISABLE,
|
|
|
|
|
# POWER_BUTTON_FORCE_ENABLE and POWER_BUTTON_FORCE_DISABLE options are
|
|
|
|
|
# mutually exclusive. One of these options must be selected in the
|
|
|
|
|
# mainboard Kconfig if the chipset supports enabling and disabling of
|
|
|
|
|
# the power button. Chipset code uses the ENABLE_POWER_BUTTON option set
|
|
|
|
|
# in mainboard/Kconfig to know if the button should be enabled or not.
|
|
|
|
|
|
|
|
|
|
config POWER_BUTTON_DEFAULT_ENABLE
|
|
|
|
|
def_bool n
|
|
|
|
|
help
|
|
|
|
|
Select when the board has a power button which can optionally be
|
|
|
|
|
disabled by the user.
|
|
|
|
|
|
|
|
|
|
config POWER_BUTTON_DEFAULT_DISABLE
|
|
|
|
|
def_bool n
|
|
|
|
|
help
|
|
|
|
|
Select when the board has a power button which can optionally be
|
|
|
|
|
enabled by the user, e.g. when the board ships with a jumper over
|
|
|
|
|
the power switch contacts.
|
|
|
|
|
|
|
|
|
|
config POWER_BUTTON_FORCE_ENABLE
|
|
|
|
|
def_bool n
|
|
|
|
|
help
|
|
|
|
|
Select when the board requires that the power button is always
|
|
|
|
|
enabled.
|
|
|
|
|
|
|
|
|
|
config POWER_BUTTON_FORCE_DISABLE
|
|
|
|
|
def_bool n
|
|
|
|
|
help
|
|
|
|
|
Select when the board requires that the power button is always
|
|
|
|
|
disabled, e.g. when it has been hardwired to ground.
|
|
|
|
|
|
|
|
|
|
config POWER_BUTTON_IS_OPTIONAL
|
|
|
|
|
bool
|
|
|
|
|
default y if POWER_BUTTON_DEFAULT_ENABLE || POWER_BUTTON_DEFAULT_DISABLE
|
|
|
|
|
default n if !(POWER_BUTTON_DEFAULT_ENABLE || POWER_BUTTON_DEFAULT_DISABLE)
|
|
|
|
|
help
|
|
|
|
|
Internal option that controls ENABLE_POWER_BUTTON visibility.
|
2013-10-31 16:26:23 +01:00
|
|
|
|
|
|
|
|
config REG_SCRIPT
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Internal option that controls whether we compile in register scripts.
|
Introduce stage-specific architecture for coreboot
Make all three coreboot stages (bootblock, romstage and ramstage) aware of the
architecture specific to that stage i.e. we will have CONFIG_ARCH variables for
each of the three stages. This allows us to have an SOC with any combination of
architectures and thus every stage can be made to run on a completely different
architecture independent of others. Thus, bootblock can have an x86 arch whereas
romstage and ramstage can have arm32 and arm64 arch respectively. These stage
specific CONFIG_ARCH_ variables enable us to select the proper set of toolchain
and compiler flags for every stage.
These options can be considered as either arch or modes eg: x86 running in
different modes or ARM having different arch types (v4, v7, v8). We have got rid
of the original CONFIG_ARCH option completely as every stage can have any
architecture of its own. Thus, almost all the components of coreboot are
identified as being part of one of the three stages (bootblock, romstage or
ramstage). The components which cannot be classified as such e.g. smm, rmodules
can have their own compiler toolset which is for now set to *_i386. Hence, all
special classes are treated in a similar way and the compiler toolset is defined
using create_class_compiler defined in Makefile.
In order to meet these requirements, changes have been made to CC, LD, OBJCOPY
and family to add CC_bootblock, CC_romstage, CC_ramstage and similarly others.
Additionally, CC_x86_32 and CC_armv7 handle all the special classes. All the
toolsets are defined using create_class_compiler.
Few additional macros have been introduced to identify the class to be used at
various points, e.g.: CC_$(class) derives the $(class) part from the name of
the stage being compiled.
We have also got rid of COREBOOT_COMPILER, COREBOOT_ASSEMBLER and COREBOOT_LINKER
as they do not make any sense for coreboot as a whole. All these attributes are
associated with each of the stages.
Change-Id: I923f3d4fb097d21071030b104c372cc138c68c7b
Signed-off-by: Furquan Shaikh <furquan@google.com>
Reviewed-on: http://review.coreboot.org/5577
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@gmail.com>
2014-04-23 19:18:48 +02:00
|
|
|
|
|
|
|
|
config MAX_REBOOT_CNT
|
|
|
|
|
int
|
|
|
|
|
default 3
|
2015-03-18 07:31:34 +01:00
|
|
|
help
|
|
|
|
|
Internal option that sets the maximum number of bootblock executions allowed
|
|
|
|
|
with the normal image enabled before assuming the normal image is defective
|
2014-07-23 18:40:02 +02:00
|
|
|
and switching to the fallback image.
|
Kconfig: Move defaults for CBFS_SIZE
We want the question for CBFS size to be next to the rom size in the
mainboard directory, but that doesn't seem to work for how people
want to set the defaults. Instead of having the list of exceptions
to the size, just set the defaults at the end of kconfig.
- Move the defaults for chipsets not setting HAVE_INTEL_FIRMWARE into
the chipset Kconfigs (gm45, nehalem, sandybridge, x4x)
- Override the default for HAVE_INTEL_FIRMWARE on skylake.
- Move the HAVE_INTEL_FIRMWARE default setting into the firmware
Kconfig file
- Move the location of the default CBFS_SIZE=ROM_SIZE to the end of
the top level kconfig file, while leaving the question where it is.
Test=rebuild Kconfig files before and after the change, verify that
they are how they were intended to be.
Note: the Skylake boards actually changed value, because they were
picking up the 0x100000 from HAVE_INTEL_FIRMWARE instead of the
0x200000 desired. This was due to the SOC_INTEL_SKYLAKE being after
the HAVE_INTEL_FIRMWARE default. Affected boards were:
Google chell, glados, & lars and Intel kunimitsu.
Change-Id: I2963a7a7eab037955558d401f5573533674a664f
Signed-off-by: Martin Roth <martinroth@google.com>
Reviewed-on: https://review.coreboot.org/13645
Tested-by: build bot (Jenkins)
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
2016-02-09 17:06:46 +01:00
|
|
|
|
2016-12-15 23:25:15 +01:00
|
|
|
config UNCOMPRESSED_RAMSTAGE
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config NO_XIP_EARLY_STAGES
|
|
|
|
|
bool
|
|
|
|
|
default n if ARCH_X86
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Identify if early stages are eXecute-In-Place(XIP).
|
|
|
|
|
|
|
|
|
|
config EARLY_CBMEM_LIST
|
|
|
|
|
bool
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
Enable display of CBMEM during romstage and postcar.
|
|
|
|
|
|
|
|
|
|
config RELOCATABLE_MODULES
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
If RELOCATABLE_MODULES is selected then support is enabled for
|
|
|
|
|
building relocatable modules in the RAM stage. Those modules can be
|
|
|
|
|
loaded anywhere and all the relocations are handled automatically.
|
|
|
|
|
|
|
|
|
|
config NO_STAGE_CACHE
|
|
|
|
|
bool
|
2018-06-25 14:38:45 +02:00
|
|
|
default y if !HAVE_ACPI_RESUME
|
2016-12-15 23:25:15 +01:00
|
|
|
help
|
|
|
|
|
Do not save any component in stage cache for resume path. On resume,
|
|
|
|
|
all components would be read back from CBFS again.
|
|
|
|
|
|
|
|
|
|
config GENERIC_GPIO_LIB
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
If enabled, compile the generic GPIO library. A "generic" GPIO
|
|
|
|
|
implies configurability usually found on SoCs, particularly the
|
|
|
|
|
ability to control internal pull resistors.
|
|
|
|
|
|
|
|
|
|
config BOOTBLOCK_CUSTOM
|
|
|
|
|
# To be selected by arch, SoC or mainboard if it does not want use the normal
|
|
|
|
|
# src/lib/bootblock.c#main() C entry point.
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config C_ENVIRONMENT_BOOTBLOCK
|
|
|
|
|
# To be selected by arch or platform if a C environment is available during the
|
|
|
|
|
# bootblock. Normally this signifies availability of RW memory (e.g. SRAM).
|
|
|
|
|
bool
|
|
|
|
|
|
2016-12-15 23:05:37 +01:00
|
|
|
###############################################################################
|
|
|
|
|
# Set default values for symbols created before mainboards. This allows the
|
|
|
|
|
# option to be displayed in the general menu, but the default to be loaded in
|
|
|
|
|
# the mainboard if desired.
|
|
|
|
|
config COMPRESS_RAMSTAGE
|
|
|
|
|
default y if !UNCOMPRESSED_RAMSTAGE
|
|
|
|
|
|
|
|
|
|
config COMPRESS_PRERAM_STAGES
|
|
|
|
|
depends on !ARCH_X86
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config INCLUDE_CONFIG_FILE
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config BOOTSPLASH_FILE
|
|
|
|
|
depends on BOOTSPLASH_IMAGE
|
|
|
|
|
default "bootsplash.jpg"
|
|
|
|
|
|
|
|
|
|
config CBFS_SIZE
|
|
|
|
|
default ROM_SIZE
|
2019-06-08 08:59:02 +02:00
|
|
|
|
|
|
|
|
config HAVE_BOOTBLOCK
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config HAVE_VERSTAGE
|
|
|
|
|
bool
|
|
|
|
|
depends on VBOOT_SEPARATE_VERSTAGE
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config HAVE_ROMSTAGE
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config HAVE_POSTCAR
|
|
|
|
|
bool
|
|
|
|
|
depends on POSTCAR_STAGE
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config HAVE_RAMSTAGE
|
|
|
|
|
bool
|
|
|
|
|
default n if RAMPAYLOAD
|
|
|
|
|
default y
|