24 Feb, 2018
18 commits
-
Integrate Boot counter for Atmel AT91SAM9XE into Kconfig
Reviewed-by: Lukasz Majewski
Signed-off-by: Alex Kiernan -
This converts the following to Kconfig:
CONFIG_BOOTCOUNT_EXTSigned-off-by: Alex Kiernan
-
This converts the following to Kconfig:
CONFIG_BOOTCOUNT_I2CSigned-off-by: Alex Kiernan
Reviewed-by: Lukasz Majewski -
This converts the following to Kconfig:
CONFIG_BOOTCOUNT_RAMSigned-off-by: Alex Kiernan
Reviewed-by: Lukasz Majewski -
This converts the following to Kconfig:
CONFIG_BOOTCOUNT_ENVSigned-off-by: Alex Kiernan
Reviewed-by: Lukasz Majewski -
This converts the following to Kconfig:
CONFIG_BOOTCOUNT_AM33XXReviewed-by: Lukasz Majewski
Reviewed-by: Hannes Schmelzer
Acked-by: Hannes Schmelzer
Signed-off-by: Alex Kiernan -
Reviewed-by: Lukasz Majewski
Signed-off-by: Alex Kiernan -
CONFIG_BOOTCOUNT was only used in mx53ppd, merge it with
CONFIG_BOOTCOUNT_LIMITSigned-off-by: Alex Kiernan
Reviewed-by: Lukasz Majewski
Reviewed-by: Ian Ray -
With the contents of config_distro_defaults.h migrated to Kconfig,
we can remove this header file completelySigned-off-by: Adam Ford
-
This converts the following to Kconfig:
CONFIG_BOOTP_BOOTPATH
CONFIG_BOOTP_DNS
CONFIG_BOOTP_GATEWAY
CONFIG_BOOTP_HOSTNAME
CONFIG_BOOTP_PXE
CONFIG_BOOTP_SUBNETMASK
CONFIG_CMDLINE_EDITING
CONFIG_AUTO_COMPLETE
CONFIG_SYS_LONGHELP
CONFIG_SUPPORT_RAW_INITRD
CONFIG_ENV_VARS_UBOOT_CONFIGSigned-off-by: Adam Ford
[trini: Re-run the migration]
Signed-off-by: Tom Rini -
The video drivers (VOP, HDMI encoder, LVDS encoder, MIPI encoder) for
Rockchip SOCs are self-contained and are mainly impacted by other
changes in the architecture support (e.g. pinctrl, clocking, etc).Let's add these to the list of files maintained as part of the
Rockchip port.Signed-off-by: Philipp Tomsich
Reviewed-by: Anatolij Gustschin -
This migrates rk_vop (the shared functions used by multiple VOP
mini-drivers) to be compatible with a live tree.Unfortunately, there's
(i) a lot of tree traversal needed for a VOP (as each active VOP
vnode references back to the endpoints in the encoders and vice
versa) to configure the connection between VOPs and encoders;
(ii) the DTS binding is not too sane and one needs to walk a node's
parents (the original code just assumed that the device would
live 3 levels above the property linked through a phandle) until
a UCLASS_DISPLAY device can be found.As part of the migration, the code for finding the enclosing display
device has been changed to not assume a specific depth of nesting
(i.e. we walk until we reach the root or find a matching device) and
to use the newly introduced (in the same series) ofnode_get_parent()
function.Signed-off-by: Philipp Tomsich
Tested-by: Klaus Goger
Reviewed-by: Anatolij Gustschin -
The rk_hdmi (shared functions for multiple HDMI mini-drivers) has been
using devfdt_get_addr() to read the HDMI controller's IO base address.
This will cause a failure with a live tree.This changes the driver to use dev_read_addr() which is safe both for
flat trees and live trees.Signed-off-by: Philipp Tomsich
Tested-by: Klaus Goger
Reviewed-by: Anatolij Gustschin -
We need to get ofnode from a phandle, add interface to support
both live dt and fdt.Signed-off-by: Kever Yang
Reviewed-by: Simon Glass
Reviewed-by: Philipp Tomsich
Tested-by: Klaus Goger
Signed-off-by: Philipp Tomsich -
The Rockchip video drivers need to walk the ofnode-parrents to find
an enclosing device that has a UCLASS_DISPLAY driver bound. This
adds a ofnode_get_parent()-function that returns the parent-node.Signed-off-by: Philipp Tomsich
Tested-by: Klaus Goger
Reviewed-by: Anatolij Gustschin
23 Feb, 2018
18 commits
-
U-Boot pulled in several core makefiles from Linux. The following
are not used in U-Boot:- CONFIG_DEBUG_SECTION_MISMATCH
- CONFIG_FTRACE_MCOUNT_RECORD
- CONFIG_GCOV_KERNEL
- CONFIG_GCOV_PROFILE_ALL
- CONFIG_KASAN
- CONFIG_MODVERSIONSWe can remove the unused code if we like. (although it will get the
scripts out of sync)CONFIG_BOOM and CONFIG_HIS_DRIVER are just mentioned in the comment
block of scripts/basic/fixdep.cCONFIG_SHELL is not configuration, but a variable for internal-use.
It is just a historical misnomer in Kbuild.Signed-off-by: Masahiro Yamada
Reviewed-by: Simon Glass -
For the omap3_logic boards, the environment is always in NAND.
This removes the ENV_IS_IN_FAT flag to eliminate the extra chatter.Signed-off-by: Adam Ford
-
Add entry for ISSI IS25LP256 part.
Signed-off-by: Marek Vasut
Cc: Jagan Teki -
Most of architectures have .text section situated in the very beginning
of U-Boot binary and thus it is very logical that CONFIG_SYS_TEXT_BASE
is used on final linkage step to specify where U-Boot gets linked to.For that we pass the following construction to the LD:
---------------------------->8-----------------------
xxx-ld ... -Ttext $(CONFIG_SYS_TEXT_BASE) ...
---------------------------->8-----------------------But there could be exceptions. For example:
1. In case of ARCv2 we want to put vectors table in its own section
.ivt in front of .text section which means we need either add an
offset to CONFIG_SYS_TEXT_BASE to compensate for .ivt or don't
pass "-Ttext" to the LD at all and specify link base in linker
script directly.2. Some architectures even though have .text section in the very
beginning of the U-Boot image still use different symbols to
specify link-base:
* NIOS2: CONFIG_SYS_MONITOR_BASE (which I really like because
that exactly what makes sense - where out image starts but not
beginning of its .text section which just happened to match the
whole image beginning)
* EXTENSA: CONFIG_SYS_TEXT_ADDR
* X86: Which doesn't use CONFIG_SYS_MONITOR_BASE in case of EFI
otherwise sets explicit link base in u-boot.ldsI think that's good to allow for flexibility and don't require each and
every architecture or even platform to specify CONFIG_SYS_TEXT_BASE as well
as use it to set .text section location.So let's only pass "-Ttext xxx" for those architectures who don't set
link-base explicitly in their linker scripts.This patch iaddresses comments for previously sent
https://patchwork.ozlabs.org/patch/867540/.Signed-off-by: Alexey Brodkin
Cc: Masahiro Yamada
Cc: Marek Vasut
Cc: Max Filippov
Cc: Simon Glass
Cc: Tom Rini -
These were dropped in [1], after relocation, for their values offset by
reloc_off.
Unconditionally show the HW values and add a '(reloc)' hint for the
offset values showed after relocation.
Also, the LRs' dumps are now formatted the same way the other regs' are.[1] Commit 082693f4 ("arm64 :show_regs: show the address before relocation")
Signed-off-by: Karl Beldan
-
Fix build after addition of RSA_get0_key() to LibreSSL.
Patch from Theo Buehler and Stuart Henderson.Signed-off-by: Theo Buehler
Signed-off-by: Stuart Henderson -
ll_temac driver was used by Xilinx Microblaze big endian and
Xilinx ppc405/ppc440 SoCs.ppc support was removed by: "powerpc: remove 4xx support"
(sha1: 98f705c9cefdfdba62c069821bbba10273a0a8ed)
and Microblaze BE is not tested for a long time that's why this driver
can be removed because none is going to updated it to DM anyway.Signed-off-by: Michal Simek
Acked-by: Joe Hershberger -
Add CONFIG_SPL_NET_VCI_STRING to enable USB-Ethernet boot mode
support.Signed-off-by: Faiz Abbas
Reviewed-by: Tom Rini -
Memory banks with address 0 and size 0 are empty and should not be
passed to the OS via device tree.Acked-by: Stephen Warren
Signed-off-by: Thierry Reding -
Do a explicit check for CONFIG_SYS_BIG_ENDIAN and
CONFIG_SYS_LITTLE_ENDIAN to avoid errors on platforms where both
are undefined (x86).Signed-off-by: Bernhard Messerklinger
Reviewed-by: Hannes Schmelzer -
Since memory banks may not be located behind each other we need to add
them separately.Signed-off-by: Bernhard Messerklinger
Reviewed-by: Hannes Schmelzer -
These got removed in config re-syncs due to a Kconfig bug. Add these
back here.Signed-off-by: Andrew F. Davis
Reviewed-by: Lokesh Vutla -
This seems to have been missed, possibly due to the inability to
enable TI_SECURE_DEVICE on Keystone2 devices previously.Fixes: bfebc8c965e4 ("env: Rename getenv_hex(), getenv_yesno(), getenv_ulong()")
Signed-off-by: Andrew F. Davis
Reviewed-by: Lokesh Vutla -
TI_SECURE_DEVICE is used by both OMAP2+ and Keystone2 family devices,
and so when ARCH_OMAP2PLUS was used to gate off the OMAP2+ Kconfig
Keystone2 family devices lost this config option.Move this option out of mach-omap2 Kconfig to a spot accessible by both
families. We picked arch/arm/Kconfig over the TI specific board/ti/
location as this option is not specific to our boards but rather our
architecture.Plus at some point this option can be changed to just
SECURE_DEVICE, as having secure parts is not exclusive to TI and
so other vendors can interpret this option as needed by their device
configurations.Fixes: a93fbf4a7892 ("ARM: omap2+: rename config to ARCH_OMAP2PLUS and consolidate Kconfig")
Signed-off-by: Andrew F. Davis
Reviewed-by: Lokesh Vutla -
Drop CONFIG_SYS_MEMORY_TOP. Rename CONFIG_SYS_TEXT_ADDR to
XTENSA_SYS_TEXT_ADDR.Signed-off-by: Max Filippov
-
A number of platforms include config_distro_defaults.h but do not enable
CONFIG_DISTRO_DEFAULTS. As they plainly intended to, set that flag and
re-sync config files.Signed-off-by: Tom Rini
-
Add DT compatible strings for RCar Gen2 SoCs, so that this driver
can bind with them. Unlike Gen3, which uses 64bit FIFO, the Gen2
uses 16bit FIFO.Signed-off-by: Marek Vasut
Cc: Jaehoon Chung
Cc: Masahiro Yamada -
With modern GCC, we get warnings such as:
cmd/jffs2.c: In function 'mtdparts_init':
arch/sh/include/asm/string.h:110:38:
warning: array subscript is above array bounds [-Warray-bounds]
: "0" (__cs), "1" (__ct), "r" (__cs+__n)
~~~~^~~~This results in a small size reduction as well.
Cc: Nobuhiro Iwamatsu
Signed-off-by: Tom Rini
22 Feb, 2018
4 commits
-
Based on reading over the GCC manual, passing both -m2a and -m2a-nofpu
are redundant, as -m2a-nofpu will provide functional code for both. As
-m2a-nofpu functions with more toolchains and does what is expected,
switch.Cc: Nobuhiro Iwamatsu
Signed-off-by: Tom Rini -
When FASTBOOT is activated, only one the supported device is supported in
code at the same time
- CONFIG_FASTBOOT_FLASH_MMC_DEV
- CONFIG_FASTBOOT_FLASH_NAND_DEVBut Today the choice is not exclusive in Kconfig
and that cause Kconfig issue when :
- CONFIG_FASTBOOT, CONFIG_MMC, CONFIG_NAND are activated
- CONFIG_FASTBOOT_FLASH_MMC_DEV = 0
- CONFIG_FASTBOOT_FLASH_NAND_DEV is not activatedThe patch add a choice in Kconfig to select the FLASH provider
- CONFIG_FASTBOOT_FLASH_MMC
- CONFIG_FASTBOOT_FLASH_NANDSigned-off-by: Patrick Delaunay
Acked-by: Maxime Ripard -
Fix two build warnings when building for arm64:
drivers/dfu/dfu_tftp.c: In function ‘dfu_tftp_write’:
drivers/dfu/dfu_tftp.c:59:37: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
ret = dfu_write_from_mem_addr(dfu, (void *)addr, len);
^
anddrivers/dfu/dfu_tftp.c: In function ‘dfu_tftp_write’:
drivers/dfu/dfu_tftp.c:41:8: warning: format ‘%u’ expects argument of type ‘unsigned int’, but argument 4 has type ‘__kernel_size_t {aka long unsigned int}’ [-Wformat=]
debug("%s: image name: %s strlen: %u\n", __func__, sb, strlen(sb));
^Signed-off-by: Marek Vasut
Cc: Lukasz Majewski -
Do the following to make the symbol names less confusing.
sed -i "s/\([TU][^_]\+\)_FUNCTION_DFU/DFU_OVER_\1/g" \
`git grep _FUNCTION_DFU | cut -d ":" -f 1 | sort -u`Signed-off-by: Marek Vasut
Cc: Lukasz Majewski
