a96e66a76f
Everything is wrong here, the Kconfig symbols are only the tip of the iceberg. Based on Kconfig prompts the SoC code performed pad configu- rations! I don't see why the person who configures coreboot should have the board schematics at hand. As a mitigation, we remove the prompts for UART_DEBUG, which is renamed to INTEL_LPSS_UART_FOR_CONSOLE (because the former didn't really say what it's about), and for UART_FOR_CONSOLE in case the former is selec- ted. Change-Id: Ibe2ed3cab0bb04bb23989c22da45299f088c758b Signed-off-by: Nico Huber <nico.h@gmx.de> Reviewed-on: https://review.coreboot.org/c/29573 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com> |
||
---|---|---|
.. | ||
acpi_tables.c | ||
board_info.txt | ||
bootblock.c | ||
brd_gpio.h | ||
devicetree.cb | ||
dsdt.asl | ||
Kconfig | ||
Kconfig.name | ||
leafhill.8192.fmd | ||
leafhill.16384.fmd | ||
mainboard.c | ||
Makefile.inc | ||
romstage.c |