mirror of
https://github.com/brain-hackers/u-boot-brain
synced 2024-08-23 02:18:51 +09:00
![]() 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> |
||
---|---|---|
.. | ||
api_display.c | ||
api_net.c | ||
api_platform-arm.c | ||
api_platform-mips.c | ||
api_platform-powerpc.c | ||
api_private.h | ||
api_storage.c | ||
api.c | ||
Kconfig | ||
Makefile | ||
README |
U-Boot machine/arch independent API for external apps ===================================================== 1. Main assumptions - there is a single entry point (syscall) to the API - per current design the syscall is a C-callable function in the U-Boot text, which might evolve into a real syscall using machine exception trap once this initial version proves functional - the consumer app is responsible for producing appropriate context (call number and arguments) - upon entry, the syscall dispatches the call to other (existing) U-Boot functional areas like networking or storage operations - consumer application will recognize the API is available by searching a specified (assumed by convention) range of address space for the signature - the U-Boot integral part of the API is meant to be thin and non-intrusive, leaving as much processing as possible on the consumer application side, for example it doesn't keep states, but relies on hints from the app and so on - optional (CONFIG_API) 2. Calls - console related (getc, putc, tstc etc.) - system (reset, platform info) - time (delay, current) - env vars (enumerate all, get, set) - devices (enumerate all, open, close, read, write); currently two classes of devices are recognized and supported: network and storage (ide, scsi, usb etc.) 3. Structure overview - core API, integral part of U-Boot, mandatory - implements the single entry point (mimics UNIX syscall) - glue - entry point at the consumer side, allows to make syscall, mandatory part - helper conveniency wrappers so that consumer app does not have to use the syscall directly, but in a more friendly manner (a la libc calls), optional part - consumer application - calls directly, or leverages the provided glue mid-layer