u-boot/board/esd/vme8349/Kconfig

if TARGET_VME8349

config SYS_BOARD
	default "vme8349"

config SYS_VENDOR
	default "esd"

config SYS_CONFIG_NAME
	default "vme8349"

endif

if TARGET_CADDY2

config SYS_BOARD
	default "vme8349"

config SYS_VENDOR
	default "esd"

config SYS_CONFIG_NAME
	default "caddy2"

endif
kconfig: add board Kconfig and defconfig files This commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig set CONFIG macros to the appropriate values for each board - configs/${TARGET_BOARD}_defconfig default setting of each board (This commit was automatically generated by a conversion script based on boards.cfg) In Linux Kernel, defconfig files are located under arch/${ARCH}/configs/ directory. It works in Linux Kernel since ARCH is always given from the command line for cross compile. But in U-Boot, ARCH is not given from the command line. Which means we cannot know ARCH until the board configuration is done. That is why all the "*_defconfig" files should be gathered into a single directory ./configs/. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: Simon Glass <sjg@chromium.org> 2014-07-30 05:08:14 +00:00			`if TARGET_VME8349`

			`config SYS_BOARD`
			`default "vme8349"`

			`config SYS_VENDOR`
			`default "esd"`

			`config SYS_CONFIG_NAME`
			`default "vme8349"`

			`endif`
mpc83xx: Make distinct caddy2 config vme8349.h contains two separate boards: The vme8349 itself, and the caddy2 board. The caddy2 board is chosen by setting certain config variables. Create a proper config file for the caddy2 board to make Kconfig migration easier. Furthermore, simplify the vme8349 and caddy2 configs by keeping only the options necessary for each board. Signed-off-by: Mario Six <mario.six@gdsys.cc> 2019-01-21 08:17:38 +00:00
			`if TARGET_CADDY2`

			`config SYS_BOARD`
			`default "vme8349"`

			`config SYS_VENDOR`
			`default "esd"`

			`config SYS_CONFIG_NAME`
			`default "caddy2"`

			`endif`