5504cdb511
Currently, we used to stitch extra VBT files to ADLRVP build using Makefile. With enablement of emerge build, we should be able to integrate more than 1 VBT binaries using ebuild. This removing these lines to avoid compilation issues in emerge builds BUG=None BRANCH=None TEST=Check if compilation passes on emerge build. Stitched additional VBT files using emerge and checked that coreboot picks up correct VBT. Change-Id: I69f1cc6c07415515ff85180fdd7cc5de11b4d805 Signed-off-by: Maulik V Vaghela <maulik.v.vaghela@intel.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/51765 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Subrata Banik <subrata.banik@intel.com> Reviewed-by: Meera Ravindranath <meera.ravindranath@intel.com> Reviewed-by: Rizwan Qureshi <rizwan.qureshi@intel.com>
25 lines
563 B
Makefile
25 lines
563 B
Makefile
## SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
subdirs-y += spd
|
|
|
|
bootblock-y += bootblock.c
|
|
bootblock-$(CONFIG_CHROMEOS) += chromeos.c
|
|
bootblock-y += early_gpio.c
|
|
|
|
verstage-$(CONFIG_CHROMEOS) += chromeos.c
|
|
|
|
romstage-$(CONFIG_CHROMEOS) += chromeos.c
|
|
romstage-y += romstage_fsp_params.c
|
|
romstage-y += board_id.c
|
|
romstage-y += memory.c
|
|
|
|
ramstage-$(CONFIG_CHROMEOS) += chromeos.c
|
|
ramstage-y += ec.c
|
|
ramstage-y += mainboard.c
|
|
ramstage-y += board_id.c
|
|
ramstage-y += gpio.c
|
|
|
|
CPPFLAGS_common += -I$(src)/mainboard/$(MAINBOARDDIR)/include
|
|
|
|
subdirs-y += variants/$(VARIANT_DIR)
|