c6588c5af9
The boot_device is a region_device that represents the device from which coreboot retrieves and boots its stages. The existing cbfs implementations use the boot_device as the intermediary for accessing the CBFS region. Also, there's currently only support for a read-only view of the boot_device. i.e. one cannot write to the boot_device using this view. However, a writable boot_device could be added in the future. Change-Id: Ic0da796ab161b8025c90631be3423ba6473ad31c Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: http://review.coreboot.org/10216 Tested-by: build bot (Jenkins) Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com> Reviewed-by: Patrick Georgi <pgeorgi@google.com>
44 lines
1.0 KiB
Makefile
44 lines
1.0 KiB
Makefile
|
|
ifeq ($(CONFIG_ARCH_ROMSTAGE_X86_32),y)
|
|
|
|
romstage-y += cbfs_and_run.c
|
|
romstage-y += memset.c
|
|
romstage-y += memcpy.c
|
|
romstage-y += memmove.c
|
|
romstage-y += rom_media.c
|
|
romstage-y += mmap_boot.c
|
|
|
|
endif # CONFIG_ARCH_ROMSTAGE_X86_32
|
|
|
|
ifeq ($(CONFIG_ARCH_RAMSTAGE_X86_32),y)
|
|
|
|
ramstage-y += c_start.S
|
|
ramstage-y += cpu.c
|
|
ramstage-y += pci_ops_conf1.c
|
|
ramstage-$(CONFIG_MMCONF_SUPPORT) += pci_ops_mmconf.c
|
|
ramstage-y += exception.c
|
|
ramstage-$(CONFIG_IOAPIC) += ioapic.c
|
|
ramstage-y += memset.c
|
|
ramstage-y += memcpy.c
|
|
ramstage-y += memmove.c
|
|
ramstage-y += ebda.c
|
|
ramstage-y += rom_media.c
|
|
ramstage-y += mmap_boot.c
|
|
ramstage-$(CONFIG_COOP_MULTITASKING) += thread.c
|
|
ramstage-$(CONFIG_COOP_MULTITASKING) += thread_switch.S
|
|
ramstage-$(CONFIG_COLLECT_TIMESTAMPS) += timestamp.c
|
|
|
|
romstage-$(CONFIG_COLLECT_TIMESTAMPS) += timestamp.c
|
|
|
|
smm-y += memset.c
|
|
smm-y += memcpy.c
|
|
smm-y += memmove.c
|
|
smm-y += rom_media.c
|
|
smm-y += mmap_boot.c
|
|
|
|
rmodules_x86_32-y += memset.c
|
|
rmodules_x86_32-y += memcpy.c
|
|
rmodules_x86_32-y += memmove.c
|
|
|
|
endif # CONFIG_ARCH_RAMSTAGE_X86_32
|