[u-boot.git] / common / Kconfig

menu "Boot timing"

config BOOTSTAGE
	bool "Boot timing and reporting"
	help
	  Enable recording of boot time while booting. To use it, insert
	  calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
	  bootstage.h. Only a single entry is recorded for each ID. You can
	  give the entry a name with bootstage_mark_name(). You can also
	  record elapsed time in a particular stage using bootstage_start()
	  before starting and bootstage_accum() when finished. Bootstage will
	  add up all the accumulated time and report it.

	  Normally, IDs are defined in bootstage.h but a small number of
	  additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
	  as the ID.

	  Calls to show_boot_progress() will also result in log entries but
	  these will not have names.

config BOOTSTAGE_REPORT
	bool "Display a detailed boot timing report before booting the OS"
	depends on BOOTSTAGE
	help
	  Enable output of a boot time report just before the OS is booted.
	  This shows how long it took U-Boot to go through each stage of the
	  boot process. The report looks something like this:

		Timer summary in microseconds:
		       Mark    Elapsed  Stage
			  0          0  reset
		  3,575,678  3,575,678  board_init_f start
		  3,575,695         17  arch_cpu_init A9
		  3,575,777         82  arch_cpu_init done
		  3,659,598     83,821  board_init_r start
		  3,910,375    250,777  main_loop
		 29,916,167 26,005,792  bootm_start
		 30,361,327    445,160  start_kernel

config BOOTSTAGE_USER_COUNT
	hex "Number of boot ID numbers available for user use"
	default 20
	help
	  This is the number of available user bootstage records.
	  Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
	  a new ID will be allocated from this stash. If you exceed
	  the limit, recording will stop.

config BOOTSTAGE_FDT
	bool "Store boot timing information in the OS device tree"
	depends on BOOTSTAGE
	help
	  Stash the bootstage information in the FDT. A root 'bootstage'
	  node is created with each bootstage id as a child. Each child
	  has a 'name' property and either 'mark' containing the
	  mark time in microseconds, or 'accum' containing the
	  accumulated time for that bootstage id in microseconds.
	  For example:

		bootstage {
			154 {
				name = "board_init_f";
				mark = <3575678>;
			};
			170 {
				name = "lcd";
				accum = <33482>;
			};
		};

	  Code in the Linux kernel can find this in /proc/devicetree.

config BOOTSTAGE_STASH
	bool "Stash the boot timing information in memory before booting OS"
	depends on BOOTSTAGE
	help
	  Some OSes do not support device tree. Bootstage can instead write
	  the boot timing information in a binary format at a given address.
	  This happens through a call to bootstage_stash(), typically in
	  the CPU's cleanup_before_linux() function. You can use the
	  'bootstage stash' and 'bootstage unstash' commands to do this on
	  the command line.

config BOOTSTAGE_STASH_ADDR
	hex "Address to stash boot timing information"
	default 0
	help
	  Provide an address which will not be overwritten by the OS when it
	  starts, so that it can read this information when ready.

config BOOTSTAGE_STASH_SIZE
	hex "Size of boot timing stash region"
	default 4096
	help
	  This should be large enough to hold the bootstage stash. A value of
	  4096 (4KiB) is normally plenty.

endmenu

menu "Boot media"

config NOR_BOOT
	bool "Support for booting from NOR flash"
	depends on NOR
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via NOR.  In this case we will enable certain pinmux early
	  as the ROM only partially sets up pinmux.  We also default to using
	  NOR for environment.

config NAND_BOOT
	bool "Support for booting from NAND flash"
	default n
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via NAND flash. This is not a must, some SoCs need this,
	  some not.

config ONENAND_BOOT
	bool "Support for booting from ONENAND"
	default n
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via ONENAND. This is not a must, some SoCs need this,
	  some not.

config QSPI_BOOT
	bool "Support for booting from QSPI flash"
	default n
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via QSPI flash. This is not a must, some SoCs need this,
	  some not.

config SATA_BOOT
	bool "Support for booting from SATA"
	default n
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via SATA. This is not a must, some SoCs need this,
	  some not.

config SD_BOOT
	bool "Support for booting from SD/EMMC"
	default n
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via SD/EMMC. This is not a must, some SoCs need this,
	  some not.

config SPI_BOOT
	bool "Support for booting from SPI flash"
	default n
	help
	  Enabling this will make a U-Boot binary that is capable of being
	  booted via SPI flash. This is not a must, some SoCs need this,
	  some not.

endmenu

config BOOTDELAY
	int "delay in seconds before automatically booting"
	default 2
	depends on AUTOBOOT
	help
	  Delay before automatically running bootcmd;
	  set to 0 to autoboot with no delay, but you can stop it by key input.
	  set to -1 to disable autoboot.
	  set to -2 to autoboot with no delay and not check for abort

	  See doc/README.autoboot for details.

menu "Console"

config CONSOLE_RECORD
	bool "Console recording"
	help
	  This provides a way to record console output (and provide console
	  input) through circular buffers. This is mostly useful for testing.
	  Console output is recorded even when the console is silent.
	  To enable console recording, call console_record_reset_enable()
	  from your code.

config CONSOLE_RECORD_OUT_SIZE
	hex "Output buffer size"
	depends on CONSOLE_RECORD
	default 0x400 if CONSOLE_RECORD
	help
	  Set the size of the console output buffer. When this fills up, no
	  more data will be recorded until some is removed. The buffer is
	  allocated immediately after the malloc() region is ready.

config CONSOLE_RECORD_IN_SIZE
	hex "Input buffer size"
	depends on CONSOLE_RECORD
	default 0x100 if CONSOLE_RECORD
	help
	  Set the size of the console input buffer. When this contains data,
	  tstc() and getc() will use this in preference to real device input.
	  The buffer is allocated immediately after the malloc() region is
	  ready.

config IDENT_STRING
	string "Board specific string to be added to uboot version string"
	help
	  This options adds the board specific name to u-boot version.

config SILENT_CONSOLE
	bool "Support a silent console"
	help
	  This option allows the console to be silenced, meaning that no
	  output will appear on the console devices. This is controlled by
	  setting the environment vaariable 'silent' to a non-empty value.
	  Note this also silences the console when booting Linux.

	  When the console is set up, the variable is checked, and the
	  GD_FLG_SILENT flag is set. Changing the environment variable later
	  will update the flag.

config SILENT_U_BOOT_ONLY
	bool "Only silence the U-Boot console"
	depends on SILENT_CONSOLE
	help
	  Normally when the U-Boot console is silenced, Linux's console is
	  also silenced (assuming the board boots into Linux). This option
	  allows the linux console to operate normally, even if U-Boot's
	  is silenced.

config SILENT_CONSOLE_UPDATE_ON_SET
	bool "Changes to the 'silent' environment variable update immediately"
	depends on SILENT_CONSOLE
	default y if SILENT_CONSOLE
	help
	  When the 'silent' environment variable is changed, update the
	  console silence flag immediately. This allows 'setenv' to be used
	  to silence or un-silence the console.

	  The effect is that any change to the variable will affect the
	  GD_FLG_SILENT flag.

config SILENT_CONSOLE_UPDATE_ON_RELOC
	bool "Allow flags to take effect on relocation"
	depends on SILENT_CONSOLE
	help
	  In some cases the environment is not available until relocation
	  (e.g. NAND). This option makes the value of the 'silent'
	  environment variable take effect at relocation.

config PRE_CONSOLE_BUFFER
	bool "Buffer characters before the console is available"
	help
	  Prior to the console being initialised (i.e. serial UART
	  initialised etc) all console output is silently discarded.
	  Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
	  buffer any console messages prior to the console being
	  initialised to a buffer. The buffer is a circular buffer, so
	  if it overflows, earlier output is discarded.

	  Note that this is not currently supported in SPL. It would be
	  useful to be able to share the pre-console buffer with SPL.

config PRE_CON_BUF_SZ
	int "Sets the size of the pre-console buffer"
	depends on PRE_CONSOLE_BUFFER
	default 4096
	help
	  The size of the pre-console buffer affects how much console output
	  can be held before it overflows and starts discarding earlier
	  output. Normally there is very little output at this early stage,
	  unless debugging is enabled, so allow enough for ~10 lines of
	  text.

	  This is a useful feature if you are using a video console and
	  want to see the full boot output on the console. Without this
	  option only the post-relocation output will be displayed.

config PRE_CON_BUF_ADDR
	hex "Address of the pre-console buffer"
	depends on PRE_CONSOLE_BUFFER
	default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
	default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
	help
	  This sets the start address of the pre-console buffer. This must
	  be in available memory and is accessed before relocation and
	  possibly before DRAM is set up. Therefore choose an address
	  carefully.

	  We should consider removing this option and allocating the memory
	  in board_init_f_init_reserve() instead.

config CONSOLE_MUX
	bool "Enable console multiplexing"
	default y if DM_VIDEO || VIDEO || LCD
	help
	  This allows multiple devices to be used for each console 'file'.
	  For example, stdout can be set to go to serial and video.
	  Similarly, stdin can be set to come from serial and keyboard.
	  Input can be provided from either source. Console multiplexing
	  adds a small amount of size to U-Boot.  Changes to the environment
	  variables stdout, stdin and stderr will take effect immediately.

config SYS_CONSOLE_IS_IN_ENV
	bool "Select console devices from the environment"
	default y if CONSOLE_MUX
	help
	  This allows multiple input/output devices to be set at boot time.
	  For example, if stdout is set to "serial,video" then output will
	  be sent to both the serial and video devices on boot. The
	  environment variables can be updated after boot to change the
	  input/output devices.

endmenu

config SYS_NO_FLASH
	bool "Disable support for parallel NOR flash"
	default n
	help
	  This option is used to disable support for parallel NOR flash.

config VERSION_VARIABLE
	bool "add U-Boot environment variable vers"
	default n
	help
	  If this variable is defined, an environment variable
	  named "ver" is created by U-Boot showing the U-Boot
	  version as printed by the "version" command.
	  Any change to this variable will be reverted at the
	  next reset.

config DISPLAY_CPUINFO
	bool "Display information about the CPU during start up"
	default y if ARM || BLACKFIN || NIOS2 || X86 || XTENSA
	help
	  Display information about the CPU that U-Boot is running on
	  when U-Boot starts up. The function print_cpuinfo() is called
	  to do this.

config DISPLAY_BOARDINFO
	bool "Display information about the board during start up"
	default y if ARM || M68K || MIPS || PPC || SPARC || XTENSA
	help
	  Display information about the board that U-Boot is running on
	  when U-Boot starts up. The board function checkboard() is called
	  to do this.

source "common/spl/Kconfig"
Commit	Line	Data
ee2b2434 SG	1	menu "Boot timing"
	2
	3	config BOOTSTAGE
	4	bool "Boot timing and reporting"
	5	help
	6	Enable recording of boot time while booting. To use it, insert
	7	calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
	8	bootstage.h. Only a single entry is recorded for each ID. You can
	9	give the entry a name with bootstage_mark_name(). You can also
	10	record elapsed time in a particular stage using bootstage_start()
	11	before starting and bootstage_accum() when finished. Bootstage will
57247d9c	12	add up all the accumulated time and report it.
ee2b2434 SG	13
ee2b2434 SG	14	Normally, IDs are defined in bootstage.h but a small number of
57247d9c	15	additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
ee2b2434 SG	16	as the ID.
ee2b2434 SG	17
57247d9c	18	Calls to show_boot_progress() will also result in log entries but
ee2b2434 SG	19	these will not have names.
	20
	21	config BOOTSTAGE_REPORT
	22	bool "Display a detailed boot timing report before booting the OS"
	23	depends on BOOTSTAGE
	24	help
	25	Enable output of a boot time report just before the OS is booted.
	26	This shows how long it took U-Boot to go through each stage of the
	27	boot process. The report looks something like this:
	28
	29	Timer summary in microseconds:
	30	Mark Elapsed Stage
	31	0 0 reset
	32	3,575,678 3,575,678 board_init_f start
	33	3,575,695 17 arch_cpu_init A9
	34	3,575,777 82 arch_cpu_init done
	35	3,659,598 83,821 board_init_r start
	36	3,910,375 250,777 main_loop
	37	29,916,167 26,005,792 bootm_start
	38	30,361,327 445,160 start_kernel
	39
	40	config BOOTSTAGE_USER_COUNT
	41	hex "Number of boot ID numbers available for user use"
	42	default 20
	43	help
	44	This is the number of available user bootstage records.
	45	Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
	46	a new ID will be allocated from this stash. If you exceed
	47	the limit, recording will stop.
	48
ee2b2434 SG	49	config BOOTSTAGE_FDT
	50	bool "Store boot timing information in the OS device tree"
	51	depends on BOOTSTAGE
	52	help
	53	Stash the bootstage information in the FDT. A root 'bootstage'
	54	node is created with each bootstage id as a child. Each child
	55	has a 'name' property and either 'mark' containing the
57247d9c	56	mark time in microseconds, or 'accum' containing the
ee2b2434 SG	57	accumulated time for that bootstage id in microseconds.
	58	For example:
	59
	60	bootstage {
	61	154 {
	62	name = "board_init_f";
	63	mark = <3575678>;
	64	};
	65	170 {
	66	name = "lcd";
	67	accum = <33482>;
	68	};
	69	};
	70
	71	Code in the Linux kernel can find this in /proc/devicetree.
	72
	73	config BOOTSTAGE_STASH
	74	bool "Stash the boot timing information in memory before booting OS"
	75	depends on BOOTSTAGE
	76	help
	77	Some OSes do not support device tree. Bootstage can instead write
	78	the boot timing information in a binary format at a given address.
	79	This happens through a call to bootstage_stash(), typically in
	80	the CPU's cleanup_before_linux() function. You can use the
	81	'bootstage stash' and 'bootstage unstash' commands to do this on
	82	the command line.
	83
	84	config BOOTSTAGE_STASH_ADDR
	85	hex "Address to stash boot timing information"
	86	default 0
	87	help
	88	Provide an address which will not be overwritten by the OS when it
	89	starts, so that it can read this information when ready.
	90
	91	config BOOTSTAGE_STASH_SIZE
	92	hex "Size of boot timing stash region"
	93	default 4096
	94	help
	95	This should be large enough to hold the bootstage stash. A value of
	96	4096 (4KiB) is normally plenty.
	97
	98	endmenu
	99
d14739ff PF	100	menu "Boot media"
	101
	102	config NOR_BOOT
	103	bool "Support for booting from NOR flash"
	104	depends on NOR
	105	help
	106	Enabling this will make a U-Boot binary that is capable of being
	107	booted via NOR. In this case we will enable certain pinmux early
	108	as the ROM only partially sets up pinmux. We also default to using
	109	NOR for environment.
	110
faaef73f PF	111	config NAND_BOOT
	112	bool "Support for booting from NAND flash"
	113	default n
	114	help
	115	Enabling this will make a U-Boot binary that is capable of being
	116	booted via NAND flash. This is not a must, some SoCs need this,
57247d9c	117	some not.
faaef73f PF	118
	119	config ONENAND_BOOT
	120	bool "Support for booting from ONENAND"
	121	default n
	122	help
	123	Enabling this will make a U-Boot binary that is capable of being
	124	booted via ONENAND. This is not a must, some SoCs need this,
57247d9c	125	some not.
faaef73f PF	126
	127	config QSPI_BOOT
	128	bool "Support for booting from QSPI flash"
	129	default n
	130	help
	131	Enabling this will make a U-Boot binary that is capable of being
	132	booted via QSPI flash. This is not a must, some SoCs need this,
57247d9c	133	some not.
faaef73f PF	134
	135	config SATA_BOOT
	136	bool "Support for booting from SATA"
	137	default n
	138	help
	139	Enabling this will make a U-Boot binary that is capable of being
	140	booted via SATA. This is not a must, some SoCs need this,
57247d9c	141	some not.
faaef73f PF	142
	143	config SD_BOOT
	144	bool "Support for booting from SD/EMMC"
	145	default n
	146	help
	147	Enabling this will make a U-Boot binary that is capable of being
	148	booted via SD/EMMC. This is not a must, some SoCs need this,
57247d9c	149	some not.
faaef73f PF	150
	151	config SPI_BOOT
	152	bool "Support for booting from SPI flash"
	153	default n
	154	help
	155	Enabling this will make a U-Boot binary that is capable of being
	156	booted via SPI flash. This is not a must, some SoCs need this,
57247d9c	157	some not.
faaef73f	158
d14739ff PF	159	endmenu
d14739ff PF	160
bb597c0e HS	161	config BOOTDELAY
bb597c0e HS	162	int "delay in seconds before automatically booting"
5e4e8741	163	default 2
41598c82	164	depends on AUTOBOOT
bb597c0e HS	165	help
bb597c0e HS	166	Delay before automatically running bootcmd;
2fbb8462	167	set to 0 to autoboot with no delay, but you can stop it by key input.
bb597c0e HS	168	set to -1 to disable autoboot.
bb597c0e HS	169	set to -2 to autoboot with no delay and not check for abort
bb597c0e	170
9060970f MY	171	See doc/README.autoboot for details.
9060970f MY	172
98af8799 SG	173	menu "Console"
98af8799 SG	174
9854a874 SG	175	config CONSOLE_RECORD
	176	bool "Console recording"
	177	help
	178	This provides a way to record console output (and provide console
57247d9c	179	input) through circular buffers. This is mostly useful for testing.
9854a874 SG	180	Console output is recorded even when the console is silent.
	181	To enable console recording, call console_record_reset_enable()
	182	from your code.
	183
	184	config CONSOLE_RECORD_OUT_SIZE
	185	hex "Output buffer size"
	186	depends on CONSOLE_RECORD
	187	default 0x400 if CONSOLE_RECORD
	188	help
	189	Set the size of the console output buffer. When this fills up, no
	190	more data will be recorded until some is removed. The buffer is
	191	allocated immediately after the malloc() region is ready.
	192
	193	config CONSOLE_RECORD_IN_SIZE
	194	hex "Input buffer size"
	195	depends on CONSOLE_RECORD
	196	default 0x100 if CONSOLE_RECORD
	197	help
	198	Set the size of the console input buffer. When this contains data,
	199	tstc() and getc() will use this in preference to real device input.
	200	The buffer is allocated immediately after the malloc() region is
	201	ready.
4d25507f	202
a4d88920 SDPP	203	config IDENT_STRING
	204	string "Board specific string to be added to uboot version string"
	205	help
	206	This options adds the board specific name to u-boot version.
	207
98af8799 SG	208	config SILENT_CONSOLE
	209	bool "Support a silent console"
	210	help
	211	This option allows the console to be silenced, meaning that no
	212	output will appear on the console devices. This is controlled by
	213	setting the environment vaariable 'silent' to a non-empty value.
	214	Note this also silences the console when booting Linux.
	215
	216	When the console is set up, the variable is checked, and the
	217	GD_FLG_SILENT flag is set. Changing the environment variable later
	218	will update the flag.
	219
	220	config SILENT_U_BOOT_ONLY
	221	bool "Only silence the U-Boot console"
	222	depends on SILENT_CONSOLE
	223	help
	224	Normally when the U-Boot console is silenced, Linux's console is
	225	also silenced (assuming the board boots into Linux). This option
	226	allows the linux console to operate normally, even if U-Boot's
	227	is silenced.
	228
	229	config SILENT_CONSOLE_UPDATE_ON_SET
	230	bool "Changes to the 'silent' environment variable update immediately"
	231	depends on SILENT_CONSOLE
	232	default y if SILENT_CONSOLE
	233	help
	234	When the 'silent' environment variable is changed, update the
	235	console silence flag immediately. This allows 'setenv' to be used
	236	to silence or un-silence the console.
	237
	238	The effect is that any change to the variable will affect the
	239	GD_FLG_SILENT flag.
	240
	241	config SILENT_CONSOLE_UPDATE_ON_RELOC
	242	bool "Allow flags to take effect on relocation"
	243	depends on SILENT_CONSOLE
	244	help
	245	In some cases the environment is not available until relocation
	246	(e.g. NAND). This option makes the value of the 'silent'
	247	environment variable take effect at relocation.
	248
8f925584 SG	249	config PRE_CONSOLE_BUFFER
	250	bool "Buffer characters before the console is available"
	251	help
	252	Prior to the console being initialised (i.e. serial UART
	253	initialised etc) all console output is silently discarded.
	254	Defining CONFIG_PRE_CONSOLE_BUFFER will cause U-Boot to
	255	buffer any console messages prior to the console being
	256	initialised to a buffer. The buffer is a circular buffer, so
	257	if it overflows, earlier output is discarded.
	258
	259	Note that this is not currently supported in SPL. It would be
	260	useful to be able to share the pre-console buffer with SPL.
	261
	262	config PRE_CON_BUF_SZ
	263	int "Sets the size of the pre-console buffer"
	264	depends on PRE_CONSOLE_BUFFER
	265	default 4096
	266	help
	267	The size of the pre-console buffer affects how much console output
	268	can be held before it overflows and starts discarding earlier
	269	output. Normally there is very little output at this early stage,
	270	unless debugging is enabled, so allow enough for ~10 lines of
	271	text.
	272
	273	This is a useful feature if you are using a video console and
	274	want to see the full boot output on the console. Without this
	275	option only the post-relocation output will be displayed.
	276
	277	config PRE_CON_BUF_ADDR
	278	hex "Address of the pre-console buffer"
	279	depends on PRE_CONSOLE_BUFFER
	280	default 0x2f000000 if ARCH_SUNXI && MACH_SUN9I
	281	default 0x4f000000 if ARCH_SUNXI && !MACH_SUN9I
	282	help
	283	This sets the start address of the pre-console buffer. This must
	284	be in available memory and is accessed before relocation and
	285	possibly before DRAM is set up. Therefore choose an address
	286	carefully.
	287
	288	We should consider removing this option and allocating the memory
	289	in board_init_f_init_reserve() instead.
	290
ef26d603 SG	291	config CONSOLE_MUX
	292	bool "Enable console multiplexing"
	293	default y if DM_VIDEO \|\| VIDEO \|\| LCD
	294	help
	295	This allows multiple devices to be used for each console 'file'.
	296	For example, stdout can be set to go to serial and video.
	297	Similarly, stdin can be set to come from serial and keyboard.
	298	Input can be provided from either source. Console multiplexing
	299	adds a small amount of size to U-Boot. Changes to the environment
	300	variables stdout, stdin and stderr will take effect immediately.
	301
	302	config SYS_CONSOLE_IS_IN_ENV
	303	bool "Select console devices from the environment"
	304	default y if CONSOLE_MUX
	305	help
	306	This allows multiple input/output devices to be set at boot time.
	307	For example, if stdout is set to "serial,video" then output will
	308	be sent to both the serial and video devices on boot. The
	309	environment variables can be updated after boot to change the
	310	input/output devices.
	311
98af8799 SG	312	endmenu
98af8799 SG	313
4d25507f SDPP	314	config SYS_NO_FLASH
	315	bool "Disable support for parallel NOR flash"
	316	default n
	317	help
	318	This option is used to disable support for parallel NOR flash.
9dd1d0aa HS	319
	320	config VERSION_VARIABLE
	321	bool "add U-Boot environment variable vers"
	322	default n
	323	help
	324	If this variable is defined, an environment variable
	325	named "ver" is created by U-Boot showing the U-Boot
	326	version as printed by the "version" command.
	327	Any change to this variable will be reverted at the
	328	next reset.
c2ae7d82	329
19a97475 LV	330	config DISPLAY_CPUINFO
	331	bool "Display information about the CPU during start up"
	332	default y if ARM \|\| BLACKFIN \|\| NIOS2 \|\| X86 \|\| XTENSA
	333	help
	334	Display information about the CPU that U-Boot is running on
	335	when U-Boot starts up. The function print_cpuinfo() is called
	336	to do this.
	337
84351792 LV	338	config DISPLAY_BOARDINFO
	339	bool "Display information about the board during start up"
	340	default y if ARM \|\| M68K \|\| MIPS \|\| PPC \|\| SPARC \|\| XTENSA
	341	help
	342	Display information about the board that U-Boot is running on
	343	when U-Boot starts up. The board function checkboard() is called
	344	to do this.
	345
c2ae7d82	346	source "common/spl/Kconfig"