mainmenu "Coreboot Configuration"
+menu "General setup"
+
+config LOCALVERSION
+ string "Local version string"
+ help
+ Append an extra string to the end of the coreboot version.
+
+ 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.
+
+endmenu
+
source src/mainboard/Kconfig
source src/arch/i386/Kconfig
source src/arch/ppc/Kconfig
-source src/devices/Kconfig
source src/northbridge/Kconfig
+source src/devices/Kconfig
source src/southbridge/Kconfig
source src/superio/Kconfig
source src/cpu/Kconfig
-config CBFS
- bool
- default y
-
-config HAVE_HIGH_TABLES
- bool
- default y
-
config PCI_BUS_SEGN_BITS
int
default 0
config MAINBOARD_PCI_SUBSYSTEM_VENDOR_ID
hex
- default 0
+ default 0x0
config MAINBOARD_PCI_SUBSYSTEM_DEVICE_ID
hex
- default 0
+ default 0x0
config CPU_ADDR_BITS
int
default 36
+config AGP_APERTURE_SIZE
+ hex
+ default 0x0
+
config XIP_ROM_BASE
hex
default 0xfffe0000
default 126
config LOGICAL_CPUS
- int
- default 1
+ bool
+ default y
config PCI_ROM_RUN
bool
default n
-config HT_CHAIN_UNITID_BASE
- int
- default 1
-
-config HT_CHAIN_END_UNITID_BASE
- int
- default 32
-
config HEAP_SIZE
hex
default 0x2000
int
default 2048
-config MULTIBOOT
- bool
- default n
-
config COMPRESSED_PAYLOAD_LZMA
bool
default y
int
default 0
-config HAVE_ACPI_TABLES
- bool
- default n
-
config HAVE_FALLBACK_BOOT
bool
default y
bool
default y
+config HAVE_FAILOVER_BOOT
+ bool
+ default n
+
+config USE_FAILOVER_IMAGE
+ bool
+ default n
+
config HAVE_HARD_RESET
bool
default n
bool
default y
-config HAVE_MP_TABLE
- bool
- default n
-
config HAVE_OPTION_TABLE
bool
default y
-config HAVE_PIRQ_TABLE
- bool
- default n
-
config PIRQ_ROUTE
bool
default n
bool
default n
+config VIDEO_MB
+ int
+ default 0
+
+config USE_WATCHDOG_ON_BOOT
+ bool
+ default n
+
+config VGA
+ bool
+ default n
+ help
+ Build board-specific VGA code.
+
+config GFXUMA
+ bool
+ default n
+ help
+ Enable Unified Memory Architecture for graphics.
+
# TODO
# menu "Drivers"
-#
+#
# endmenu
-menu "Payload"
+menu "System tables"
-config COMPRESSED_PAYLOAD_LZMA
- bool "Use LZMA compression for payloads"
- default yes
+config HAVE_LOW_TABLES
+ bool
+ default y
+
+config HAVE_HIGH_TABLES
+ bool "Write 'high' tables to avoid being overwritten in F segment"
+ default y
+
+config MULTIBOOT
+ bool "Generate Multiboot tables (for GRUB2)"
+ default n
+
+config HAVE_ACPI_TABLES
+ bool "Generate ACPI tables"
+ default n
+
+config HAVE_MP_TABLE
+ bool "Generate an MP table"
+ default n
+
+config HAVE_PIRQ_TABLE
+ bool "Generate a PIRQ table"
+ default n
+
+endmenu
+
+menu "Payload"
choice
- prompt "Payload type"
+ prompt "Add a payload"
default PAYLOAD_NONE
+config PAYLOAD_NONE
+ bool "None"
+ help
+ Select this option if you want to create an "empty" coreboot
+ ROM image for a certain mainboard, i.e. a coreboot ROM image
+ which does not yet contain a payload.
+
+ For such an image to be useful, you have to use 'cbfstool'
+ to add a payload to the ROM image later.
+
config PAYLOAD_ELF
- bool "An ELF executable payload file"
+ bool "An ELF executable payload"
help
Select this option if you have a payload image (an ELF file)
which coreboot should run as soon as the basic hardware
You will be able to specify the location and file name of the
payload image later.
-config PAYLOAD_NONE
- bool "No payload"
- help
- Select this option if you want to create an "empty" coreboot
- ROM image for a certain mainboard, i.e. a coreboot ROM image
- which does not yet contain a payload.
-
- For such an image to be useful, you have to use the 'cbfs' tool
- to add a payload to the ROM image later.
endchoice
help
The path and filename of the ELF executable file to use as payload.
+# TODO: Defined if no payload? Breaks build?
+config COMPRESSED_PAYLOAD_LZMA
+ bool "Use LZMA compression for payloads"
+ default y
+ depends on PAYLOAD_ELF
+ help
+ In order to reduce the size payloads take up in the ROM chip
+ coreboot can compress them using the LZMA algorithm.
+
endmenu
menu "VGA BIOS"
depends on VGA_BIOS
default "1106,3230"
help
- The ID that would associate your VGA BIOS to your video card.
- (PCI VendorID, PCI Device ID)
+ The comma-separated PCI vendor and device ID that would associate
+ your VGA BIOS to your video card.
+
+ Example: 1106,3230
+
+ In the above example 1106 is the PCI vendor ID (in hex, but without
+ the "0x" prefix) and 3230 specifies the PCI device ID of the
+ video card (also in hex, without "0x" prefix).
endmenu
+menu "Debugging"
+
+# TODO: Better help text and detailed instructions.
config GDB_STUB
bool "GDB debugging support"
default y
If enabled, you will be able to set breakpoints for gdb debugging.
See src/arch/i386/lib/c_start.S for details.
+endmenu
+