fbb11cf979
It might be that you want an early console in romstage before RAM is up, but you can't or don't want to support the console all the way back in the bootblock. By making the console in those two different environments configurable seperately that becomes possible. On the 5250 console output as early as the bootblock works, but on the 5420 it only starts working in the ROM stage after clocks have been initialized. Change-Id: I68ae3fcb4d828fa8a328a30001c23c81a4423bb8 Signed-off-by: Gabe Black <gabeblack@chromium.org> Reviewed-on: http://review.coreboot.org/3671 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
33 lines
1 KiB
Makefile
33 lines
1 KiB
Makefile
ramstage-y += printk.c
|
|
ramstage-y += console.c
|
|
ramstage-y += vtxprintf.c
|
|
ramstage-y += vsprintf.c
|
|
ramstage-y += post.c
|
|
ramstage-y += die.c
|
|
|
|
smm-y += printk.c
|
|
smm-y += vtxprintf.c
|
|
smm-$(CONFIG_SMM_TSEG) += die.c
|
|
|
|
romstage-$(CONFIG_EARLY_CONSOLE) += vtxprintf.c
|
|
romstage-y += console.c
|
|
romstage-y += post.c
|
|
romstage-y += die.c
|
|
|
|
bootblock-$(CONFIG_BOOTBLOCK_CONSOLE) += vtxprintf.c
|
|
bootblock-y += console.c
|
|
bootblock-y += die.c
|
|
|
|
ramstage-$(CONFIG_CONSOLE_SERIAL8250) += uart8250_console.c
|
|
ramstage-$(CONFIG_CONSOLE_SERIAL8250MEM) += uart8250mem_console.c
|
|
ramstage-$(CONFIG_SPKMODEM) += spkmodem_console.c
|
|
ramstage-$(CONFIG_USBDEBUG) += usbdebug_console.c
|
|
ramstage-$(CONFIG_CONSOLE_LOGBUF) += logbuf_console.c
|
|
ramstage-$(CONFIG_CONSOLE_NE2K) += ne2k_console.c
|
|
ramstage-$(CONFIG_CONSOLE_CBMEM) += cbmem_console.c
|
|
ramstage-$(CONFIG_CONSOLE_QEMU_DEBUGCON) += qemu_debugcon_console.c
|
|
|
|
|
|
$(obj)/console/console.ramstage.o : $(obj)/build.h
|
|
$(obj)/console/console.romstage.o : $(obj)/build.h
|
|
$(obj)/console/console.bootblock.o : $(obj)/build.h
|