SPDX: Convert all of our single license tags to Linux Kernel styleWhen U-Boot started using SPDX tags we were among the early adopters andthere weren't a lot of other examples to borrow from. So
SPDX: Convert all of our single license tags to Linux Kernel styleWhen U-Boot started using SPDX tags we were among the early adopters andthere weren't a lot of other examples to borrow from. So we picked thearea of the file that usually had a full license text and replaced itwith an appropriate SPDX-License-Identifier: entry. Since then, theLinux Kernel has adopted SPDX tags and they place it as the very firstline 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 visibilityand in part for other minor reasons, switch over to that style.This commit changes all instances where we have a single declaredlicense in the tag as both the before and after are identical in tagcontents. There's also a few places where I found we did not have a tagand have introduced one.Signed-off-by: Tom Rini <trini@konsulko.com>
show more ...
ARM: tegra: move NVIDIA common files to arch/arm/mach-tegraAll the Tegra boards borrow the files from board/nvidia/common/directory, i.e., board/nvidia/common/* are not vendor-common files,but So
ARM: tegra: move NVIDIA common files to arch/arm/mach-tegraAll the Tegra boards borrow the files from board/nvidia/common/directory, i.e., board/nvidia/common/* are not vendor-common files,but SoC-common files.Move NVIDIA common files to arch/arm/mach-tegra/ to clean upMakefiles.As arch/arm/mach-tegra/board.c already exists, this commit renamesboard/nvidia/common/board.c to arch/arm/mach-tegra/board2.c,expecting they will be consolidated as a second step.Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>Cc: Stephen Warren <swarren@nvidia.com>Cc: Tom Warren <twarren@nvidia.com>Cc: Simon Glass <sjg@chromium.org>Acked-by: Simon Glass <sjg@chromium.org>Signed-off-by: Tom Warren <twarren@nvidia.com>
kconfig: remove redundant "string" type in arch and board KconfigsNow the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}are specified in arch/Kconfig.We can delete the ones in
kconfig: remove redundant "string" type in arch and board KconfigsNow the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}are specified in arch/Kconfig.We can delete the ones in arch and board Kconfig files.This commit can be easily reproduced by the following command:find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '/config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ { N s/\n[[:space:]]*string//}'Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
tegra: kconfig: move board select menu and common settingsBecuase the board select menu in arch/arm/Kconfig is too big,move the Tegra board select menu to tegra/Kconfig.Insert the Tegra SoC sele
tegra: kconfig: move board select menu and common settingsBecuase the board select menu in arch/arm/Kconfig is too big,move the Tegra board select menu to tegra/Kconfig.Insert the Tegra SoC select menu between the arch select and theboard select. Architecture select |-- Tegra Platform (Tegra) |- Tegra SoC select (Tegra20 / 30 / 114 / 124) |- Board selectConsolidate also common settings (CONFIG_SYS_CPU="armv7" andCONFIG_SYS_SOC="tegra*") and always "select" CONFIG_SPL as follows: config TEGRA bool select SPLSigned-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Acked-by: Stephen Warren <swarren@nvidia.com>Cc: Tom Warren <twarren@nvidia.com>
Add board MAINTAINERS filesWe have switched to Kconfig and the boards.cfg file is going tobe removed. We have to retrieve the board status and maintainersinformation from it.The MAINTAINERS for
Add board MAINTAINERS filesWe have switched to Kconfig and the boards.cfg file is going tobe removed. We have to retrieve the board status and maintainersinformation from it.The MAINTAINERS format as in Linux Kernel would be nicebecause we can crib the scripts/get_maintainer.pl script.After some discussion, we chose to put a MAINTAINERS file under eachboard directory, not the top-level one because we want to collectrelevant information for a board into a single place.TODO:Modify get_maintainer.pl to scan multiple MAINTAINERS files.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Suggested-by: Tom Rini <trini@ti.com>Acked-by: Simon Glass <sjg@chromium.org>
kconfig: add board Kconfig and defconfig filesThis commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
kconfig: add board Kconfig and defconfig filesThis commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig set CONFIG macros to the appropriate values for each board - configs/${TARGET_BOARD}_defconfig default setting of each board(This commit was automatically generated by a conversion scriptbased on boards.cfg)In Linux Kernel, defconfig files are located underarch/${ARCH}/configs/ directory.It works in Linux Kernel since ARCH is always given from thecommand line for cross compile.But in U-Boot, ARCH is not given from the command line.Which means we cannot know ARCH until the board configuration is done.That is why all the "*_defconfig" files should be gathered into asingle directory ./configs/.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Acked-by: Simon Glass <sjg@chromium.org>
kbuild: change out-of-tree buildThis commit changes the working directorywhere the build process occurs.Before this commit, build process occurred under the sourcetree for both in-tree and out-
kbuild: change out-of-tree buildThis commit changes the working directorywhere the build process occurs.Before this commit, build process occurred under the sourcetree for both in-tree and out-of-tree build.That's why we needed to add $(obj) prefix to all generatedfiles in makefiles like follows: $(obj)u-boot.bin: $(obj)u-bootHere, $(obj) is empty for in-tree build, whereas it pointsto the output directory for out-of-tree build.And our old build system changes the current working directorywith "make -C <sub-dir>" syntax when descending into thesub-directories.On the other hand, Kbuild uses a different ideato handle out-of-tree build and directory descending.The build process of Kbuild always occurs under the output tree.When "O=dir/to/store/output/files" is given, the build systemchanges the current working directory to that directory andrestarts the make.Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj=<sub-dir>"syntax for descending into sub-directories.(We can write it like "make $(obj)=<sub-dir>" with a shorthand.)This means the current working directory is always the topof the output directory.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Tested-by: Gerhard Sittig <gsi@denx.de>
board: tec-ng: Do not make directories in a board MakefileCommit e5c5301f refactored the build system not to makedirectories in board makefiles.But commit 8f380381 create directories again inboa
board: tec-ng: Do not make directories in a board MakefileCommit e5c5301f refactored the build system not to makedirectories in board makefiles.But commit 8f380381 create directories again inboard/avionic-design/tec-ng/Makefile.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Cc: Alban Bedel <alban.bedel@avionic-design.de>
ARM: tegra: Add the Tamonten™ NG Evaluation Carrier boardAdd support for the new Tamonten™ NG platform from Avionic Design.Currently only I2C, MMC, USB and ethernet have been tested.Signed-off-b
ARM: tegra: Add the Tamonten™ NG Evaluation Carrier boardAdd support for the new Tamonten™ NG platform from Avionic Design.Currently only I2C, MMC, USB and ethernet have been tested.Signed-off-by: Alban Bedel <alban.bedel@avionic-design.de>Reviewed-by: Stephen Warren <swarren@nvidia.com>Signed-off-by: Tom Warren <twarren@nvidia.com>