mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-12 22:33:18 +00:00
83d290c56f
When U-Boot started using SPDX tags we were among the early adopters and there weren't a lot of other examples to borrow from. So we picked the area of the file that usually had a full license text and replaced it with an appropriate SPDX-License-Identifier: entry. Since then, the Linux Kernel has adopted SPDX tags and they place it as the very first line in a file (except where shebangs are used, then it's second line) and with slightly different comment styles than us. In part due to community overlap, in part due to better tag visibility and in part for other minor reasons, switch over to that style. This commit changes all instances where we have a single declared license in the tag as both the before and after are identical in tag contents. There's also a few places where I found we did not have a tag and have introduced one. Signed-off-by: Tom Rini <trini@konsulko.com> |
||
---|---|---|
.. | ||
acpi | ||
.gitignore | ||
conga-qeval20-qa3.c | ||
dsdt.asl | ||
Kconfig | ||
MAINTAINERS | ||
Makefile | ||
README | ||
start.S |
------------------------------ U-Boot console UART selection: ------------------------------ The U-Boot port for this congatec board currently supports two different configurations (defconfig files). The only difference is the UART that is used as the U-Boot console UART. The default defconfig file: conga-qeval20-qa3-e3845_defconfig provides this console on the UART0 which is provided via a Winbond Super-IO chip connected on the congatec Qseven 2.0 evaluation carrier board (conga-QEVAL). This UART is the one provided with a SubD9 connector on the mainboard (the low one). The 2nd defconfig file: conga-qeval20-qa3-e3845-internal-uart_defconfig provides the U-Boot console on the BayTrail internal legacy UART, which is routed from the QSeven SoM to the X300 connector on the baseboard. Here is called COM2. The baseboard already provides the RS232 level shifters. So a TTL-USB UART adapter does not work in this case. The signals need to get connected directly to the RS232 level signals of the PC UART via some adapter cable.