UPSTREAM: 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 header
UPSTREAM: 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>Change-Id: I6c0f7e50e8b571106627f25ddac008a62bd2994eReported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
show more ...
board_f: Rename initdram() to dram_init()This allows us to use the same DRAM init function on all archs. Add adummy function for arc, which does not use DRAM init here.Signed-off-by: Simon Glass
board_f: Rename initdram() to dram_init()This allows us to use the same DRAM init function on all archs. Add adummy function for arc, which does not use DRAM init here.Signed-off-by: Simon Glass <sjg@chromium.org>[trini: Dummy function on nios2]Signed-off-by: Tom Rini <trini@konsulko.com>
board_f: Drop return value from initdram()At present we cannot use this function as an init sequence call without awrapper, since it returns the RAM size. Adjust it to set the RAM size inglobal_d
board_f: Drop return value from initdram()At present we cannot use this function as an init sequence call without awrapper, since it returns the RAM size. Adjust it to set the RAM size inglobal_data instead, and return 0 on success.Signed-off-by: Simon Glass <sjg@chromium.org>Reviewed-by: Stefan Roese <sr@denx.de>
board_f: Drop board_type parameter from initdram()It looks like only cm5200 and tqm8xx use this feature, so we don't reallyneed it in generic code. Drop it and have the users access gd->board_type
board_f: Drop board_type parameter from initdram()It looks like only cm5200 and tqm8xx use this feature, so we don't reallyneed it in generic code. Drop it and have the users access gd->board_typedirectly.Signed-off-by: Simon Glass <sjg@chromium.org>Reviewed-by: Stefan Roese <sr@denx.de>
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>
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>
mpc83xx: add ids8313 supportadd support for the ids8313 board.CPU: e300c3, MPC8313, Rev: 2.1 at 396 MHz, CSB: 132 MHzI2C: readySPI: readyDRAM: 128 MiB (DDR2, 32-bit, ECC off, 264 MHz)F
mpc83xx: add ids8313 supportadd support for the ids8313 board.CPU: e300c3, MPC8313, Rev: 2.1 at 396 MHz, CSB: 132 MHzI2C: readySPI: readyDRAM: 128 MiB (DDR2, 32-bit, ECC off, 264 MHz)Flash: 8 MiBNAND: 128 MiBNet: TSEC0, TSEC1 [PRIME]public key on NOR flash startSigned-off-by: Heiko Schocher <hs@denx.de>Signed-off-by: Kim Phillips <kim.phillips@freescale.com>