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 ...
libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h>Thomas reported U-Boot failed to build host tools if libfdt-develpackage is installed because tools include libfdt headers from/us
libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h>Thomas reported U-Boot failed to build host tools if libfdt-develpackage is installed because tools include libfdt headers from/usr/include/ instead of using internal ones.This commit moves the header code: include/libfdt.h -> include/linux/libfdt.h include/libfdt_env.h -> include/linux/libfdt_env.hand replaces include directives: #include <libfdt.h> -> #include <linux/libfdt.h> #include <libfdt_env.h> -> #include <linux/libfdt_env.h>Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Add more SPDX-License-Identifier tagsIn a number of places we had wordings of the GPL (or LGPL in a fewcases) license text that were split in such a way that it wasn't caughtpreviously. Convert
Add more SPDX-License-Identifier tagsIn a number of places we had wordings of the GPL (or LGPL in a fewcases) license text that were split in such a way that it wasn't caughtpreviously. Convert all of these to the correct SPDX-License-Identifiertag.Signed-off-by: Tom Rini <trini@konsulko.com>
powerpc: xes: Add maintainerAdd Peter Tyser as the maintainer of Extreme Engineering Solutions products.Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
fdt: Allow ft_board_setup() to report failureThis function can fail if the device tree runs out of space. Rather thansilently booting with an incomplete device tree, allow the failure to bedetect
fdt: Allow ft_board_setup() to report failureThis function can fail if the device tree runs out of space. Rather thansilently booting with an incomplete device tree, allow the failure to bedetected.Unfortunately this involves changing a lot of places in the code. I havenot changed behvaiour to return an error where one is not currentlyreturned, to avoid unexpected breakage.Eventually it would be nice to allow boards to register functions to becalled to update the device tree. This would avoid all the many functionsto do this. However it's not clear yet if this should be done using drivermodel or with a linker list. This work is left for later.Signed-off-by: Simon Glass <sjg@chromium.org>Acked-by: Anatolij Gustschin <agust@denx.de>
MAINTAINERS: comment out blank M: fieldSince commit ddaf5c8f3030050fcd356a1e49e3ee8f8f52c6d4(patman: RunPipe() should not pipe stdout/stderr unless asked),Patman spits lots of "Invalid MAINTAINER
MAINTAINERS: comment out blank M: fieldSince commit ddaf5c8f3030050fcd356a1e49e3ee8f8f52c6d4(patman: RunPipe() should not pipe stdout/stderr unless asked),Patman spits lots of "Invalid MAINTAINERS address: '-'"error messages for patches with global changes.It takes too long for Patman to process them.Anyway, "M: -" does not carry any important information.Rather, it is just like a place holder in case of assigninga new board maintainer. Let's comment out.This commit can be reproduced by the following command:find . -name MAINTAINERS | xargs sed -i -e '/^M:[[:blank:]]*-$/s/^/#/'Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.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>
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>
Driver/DDR: Moving Freescale DDR driver to a common driverFreescale DDR driver has been used for mpc83xx, mpc85xx, mpc86xx SoCs.The similar DDR controllers will be used for ARM-based SoCs.Signed
Driver/DDR: Moving Freescale DDR driver to a common driverFreescale DDR driver has been used for mpc83xx, mpc85xx, mpc86xx SoCs.The similar DDR controllers will be used for ARM-based SoCs.Signed-off-by: York Sun <yorksun@freescale.com>
board: powerpc: convert makefiles to Kbuild styleSigned-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Cc: Wolfgang Denk <wd@denx.de>Cc: Kim Phillips <kim.phillips@freescale.com>Cc: York Sun
board: powerpc: convert makefiles to Kbuild styleSigned-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Cc: Wolfgang Denk <wd@denx.de>Cc: Kim Phillips <kim.phillips@freescale.com>Cc: York Sun <yorksun@freescale.com>Cc: Stefan Roese <sr@denx.de>
Add GPL-2.0+ SPDX-License-Identifier to source filesSigned-off-by: Wolfgang Denk <wd@denx.de>[trini: Fixup common/cmd_io.c]Signed-off-by: Tom Rini <trini@ti.com>
punt unused clean/distclean targetsThe top level Makefile does not do any recursion into subdirs whencleaning, so these clean/distclean targets in random arch/board dirsnever get used. Punt them
punt unused clean/distclean targetsThe top level Makefile does not do any recursion into subdirs whencleaning, so these clean/distclean targets in random arch/board dirsnever get used. Punt them all.MAKEALL didn't report any errors related to this that I could see.Signed-off-by: Mike Frysinger <vapier@gentoo.org>
powerpc/8xxx: Refactor fsl_ddr_get_spd into common code from boardMove fsl_ddr_get_spd into common mpc8xxx/ddr/main.c as most boardspretty much do the same thing. The only variations are in how m
powerpc/8xxx: Refactor fsl_ddr_get_spd into common code from boardMove fsl_ddr_get_spd into common mpc8xxx/ddr/main.c as most boardspretty much do the same thing. The only variations are in how manycontrollers or DIMMs per controller exist. To make this work westandardize on the names of the SPD_EEPROM_ADDRESS defines based on theuse case of the board.We allow boards to override get_spd to either do board specific fixupsto the SPD data or deal with any unique behavior of how the SPD eepromsare wired up.Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
powerpc/8xxx: Replace fsl_ddr_get_mem_data_rate with get_ddr_freq()Every 85xx board implements fsl_ddr_get_mem_data_rate via get_ddr_freq()and every 86xx board uses get_bus_freq(). If implement g
powerpc/8xxx: Replace fsl_ddr_get_mem_data_rate with get_ddr_freq()Every 85xx board implements fsl_ddr_get_mem_data_rate via get_ddr_freq()and every 86xx board uses get_bus_freq(). If implement get_ddr_freq()as a static inline to call get_bus_freq() we can removefsl_ddr_get_mem_data_rate altogether and just call get_ddr_freq()directly.Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Replace "FLASH" strings with "Flash" or "flash"There's no compelling reason to have the output on bootup or the"flinfo" command print "flash" in uppercase, so use the proper casewhere appropriate
Replace "FLASH" strings with "Flash" or "flash"There's no compelling reason to have the output on bootup or the"flinfo" command print "flash" in uppercase, so use the proper casewhere appropriate.Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
powerpc/8xxx: Rework XES boards pci_init_board to use common FSL PCIe codeRemove duplicated code in MPC8xxx XES boards and utilize the commonfsl_pcie_init_board().Signed-off-by: Kumar Gala <gala
powerpc/8xxx: Rework XES boards pci_init_board to use common FSL PCIe codeRemove duplicated code in MPC8xxx XES boards and utilize the commonfsl_pcie_init_board().Signed-off-by: Kumar Gala <galak@kernel.crashing.org>CC: Peter Tyser <ptyser@xes-inc.com>
Switch from archive libraries to partial linkingBefore this commit, weak symbols were not overridden by non-weak symbolsfound in archive libraries when linking with recent versions ofbinutils. A
Switch from archive libraries to partial linkingBefore this commit, weak symbols were not overridden by non-weak symbolsfound in archive libraries when linking with recent versions ofbinutils. As stated in the System V ABI, "the link editor does notextract archive members to resolve undefined weak symbols".This commit changes all Makefiles to use partial linking (ld -r) insteadof creating library archives, which forces all symbols to participate inlinking, allowing non-weak symbols to override weak symbols as intended.This approach is also used by Linux, from which the gmake functioncmd_link_o_target (defined in config.mk and used in all Makefiles) isinspired.The name of each former library archive is preserved except forextensions which change from ".a" to ".o". This commit updatesreferences accordingly where needed, in particular in some linkerscripts.This commit reveals board configurations that exclude some features butinclude source files that depend these disabled features in the build,resulting in undefined symbols. Known such cases include:- disabling CMD_NET but not CMD_NFS;- enabling CONFIG_OF_LIBFDT but not CONFIG_QE.Signed-off-by: Sebastien Carlier <sebastien.carlier@gmail.com>
xes: Make X-ES board names more genericSome U-Boot images for X-ES boards support multiple products in the samefamily. For example, the XPedite5370, XPedite5371, and XPedite5372 aresimilar enoug
xes: Make X-ES board names more genericSome U-Boot images for X-ES boards support multiple products in the samefamily. For example, the XPedite5370, XPedite5371, and XPedite5372 aresimilar enough that one U-Boot image can work on all 3 cards. To make itclear that a U-Boot image can work on boards of the same family, renamethe boards with the least significant digit of 'x'.While we're at it, change the board config file and make targets to belowercase.Also change the default uImage and fdt filenames to "board.uImage" and"board.dtb" to be more generic.Signed-off-by: Peter Tyser <ptyser@xes-inc.com>Signed-off-by: Kumar Gala <galak@kernel.crashing.org>