To debug device tree issues involving 32- and 64-bit platforms, it is useful to
have a generic 64-bit platform available.

Add a version of the sandbox that uses 64-bit integers for its physical
addresses as well as a modified device tree.
Signed-off-by: NMario Six <mario.six@gdsys.cc>
Added CONFIG_SYS_TEXT_BASE to configs/sandbox64_defconfig
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present dtc produces these warnings when compiling sandbox:

arch/sandbox/dts/test.dtb: Warning (gpios_property):
	Could not get phandle node for /base-gpios:num-gpios(cell 0)
arch/sandbox/dts/test.dtb: Warning (gpios_property):
	Missing property '#gpio-cells' in node /reset-ctl or bad phandle
	(referred from /extra-gpios:num-gpios[0])

Both are due to it assuming that the 'num-gpios' property holds a phandle
pointing to a GPIO node.

To avoid these warnings, rename the sandbox property so that it does not
include the string 'gpios'.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present dtc produces these warnings when compiling sandbox:

arch/sandbox/dts/test.dtb: Warning (reg_format): "reg" property in /chosen/chosen-test has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
arch/sandbox/dts/test.dtb: Warning (avoid_default_addr_size): Relying on default #address-cells value for /chosen/chosen-test
arch/sandbox/dts/test.dtb: Warning (avoid_default_addr_size): Relying on default #size-cells value for /chosen/chosen-test

Add the missing properties to avoid this.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Fixes: f2006808 (dm: core: parse chosen node)

Memory banks with address 0 and size 0 are empty and should not be
passed to the OS via device tree.
Signed-off-by: NThierry Reding <treding@nvidia.com>
Acked-by: NStephen Warren <swarren@nvidia.com>

Only ARM and in some configs MIPS really implement arch_fixup_fdt().
Others just use the same boilerplate which is not good by itself,
but what's worse if we try to build with disabled CONFIG_CMD_BOOTM
and enabled CONFIG_OF_LIBFDT we'll hit an unknown symbol which was
apparently implemented in arch/xxx/lib/bootm.c.

Now with weak arch_fixup_fdt() right in image-fdt.c where it is
used we get both items highlighted above fixed.
Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com>
Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
Cc: York Sun <york.sun@nxp.com>
Cc: Stefan Roese <sr@denx.de>
Reviewed-by: NTom Rini <trini@konsulko.com>
Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>

Commit 958d55f2 ("MAINTAINERS: Take over BCM2835 maintainership") put
me in as maintainer for the RPi soc, but forgot to update the board
MAINTAINERS file.

Add me there too.
Signed-off-by: NAlexander Graf <agraf@suse.de>

ARC Elf32 tools by default enable usage of so-called "small data"
section or in ARC PRM parlance "GP-relative addressing".

The idea is to put up to 2kB of frequently used data into a separate
location and use indirect addressing via dedicated core register (GP).
Where GP is used as a base for offset calculation.

And so if "-msdata" toggle is passed to the compiler either explicitly
or implicitly (that's Elf32 tools case) it will try to put some data
in that "small data" area and then to calculate real offset from GP
to be encoded in instructions we need to know the base value which
liker gets from __SDATA_BEGIN__ symbol in hte linker script.

In U-Boot we don't use that feature and linker script doesn't define
__SDATA_BEGIN__ which gives us the following linkage error if we use
Elf32 tools:
------------------------->8-------------------
  LD      u-boot
.../bin/arc-elf32-ld.bfd: Error: Linker symbol __SDATA_BEGIN__ not found
.../bin/arc-elf32-ld.bfd: final link failed: Bad value
------------------------->8-------------------

Note if uClibc or glibc tools are used that problem doesn't happen
because usage of "small data section" is disabled by default as not very
useful for bigger executables. Moreover GP is just another name of r26
so we're loosing 1 core register which is not used by the compiler as a
generic register with "-msdata".
Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com>

This converts the following to Kconfig:
   CONFIG_SYS_BOOTCOUNT_SINGLEWORD
Signed-off-by: NLukasz Majewski <lukma@denx.de>
Tested-by: NAlex Kiernan <alex.kiernan@gmail.com>
Reviewed-by: NIan Ray <ian.ray@ge.com>

This converts the following to Kconfig:
   CONFIG_BOOTCOUNT_LIMIT
Signed-off-by: NLukasz Majewski <lukma@denx.de>
Tested-by: NAlex Kiernan <alex.kiernan@gmail.com>
Reviewed-by: NHannes Schmelzer <hannes.schmelzer@br-automation.com>
Acked-by: NHannes Schmelzer <hannes.schmelzer@br-automation.com>

Rsync all defconfig files using moveconfig.py
Signed-off-by: NTom Rini <trini@konsulko.com>

Upon further review, not all code authors are in favour of this change.
This reverts commit ee3556bc.
Signed-off-by: NTom Rini <trini@konsulko.com>

With commit 9bd76b80 ("spl: make CONFIG_OF_EMBED pass dts through
fdtgrep"), CONFIG_SPL_MULTI_DTB_FIT has been broken because
cmd_fdtgrep was now unknown in scripts/Makefile.spl after moving
it to dts/Makefile. This bug has been introduced with v2018.01.

This patch moves cmd_fdtgrep from dts/Makefile to scripts/Makefile.lib
and includes scripts/Makefile.lib in scripts/Makefile.spl.

Fixes: 9bd76b80 ("spl: make CONFIG_OF_EMBED pass dts through fdtgrep")
Reported-by: NLokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: NSimon Goldschmidt <sgoldschmidt@de.pepperl-fuchs.com>
Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>

Configuration option CMD_SCSI should be placed in the same submenu as
CMD_SATA and CMD_MMC.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

ATF recently began announcing PSCI v1.1. Since that version is unknown
to u-boot, the PSCI device nodes were not updated.

Switch from the case statement to a greater/less-than comparison so that
v1.1, as well as future versions, get at least the compatible nodes of
known versions.

PSCI v1.1 doesn't seem to have introduced a new corresponding compatible.
Signed-off-by: NAndre Heider <a.heider@gmail.com>

The single argument `--noheader' is expecting isn't taken from getopt
parsing, but instead from the remaining argv arguments.
Signed-off-by: NAlex Kiernan <alex.kiernan@gmail.com>

>From DFU_ALT_INFO_EMMC (include/environment/ti/dfu.h) we can see that
rootfs will be flashed to second partition on eMMC. But at the moment we
have only one partition in $partitions environment variable. Let's add
"bootloader" partition prior to "rootfs", so that DFU works correctly.
This also fixes eMMC boot, which looks for rootfs on second partition.

"bootloader" partition start corresponds to "u-boot.img.raw" in DFU
eMMC info, which is 0x300 sector (384 KiB offset from eMMC start).

rootfs start address can be also found from DFU eMMC info.
bootloader-related area is finished at 0x1500 sector (2688 KiB offset
from eMMC start). This should be the start address for rootfs in
$partitions environment variable.

While at it, fix U-Boot environment address to be the same as for
AM57x EVM, so that it doesn't clash with other partitions.

So now eMMC layout looks like this:

    ===============================================================

    0       +------------------------+
            | MBR/GPT header         |   128           -
    128     +------------------------+
            | MLO                    |   256           -
    384     +------------------------+
            | u-boot.img             |   1792          bootloader
    2176    +------------------------+
            | //////// hole //////// |   256           -
    2432    +------------------------+
            | U-Boot environment     |   128           -
    2560    +------------------------+
            | U-Boot environment     |   128           -
            | (redundant)            |
    2688    +------------------------+
            | rootfs                 |   remaining     rootfs
    end     +------------------------+

    ===============================================================

"hole" area can be used further for storing U-Boot environment (like
it's done in AM57x EVM config file) or for increasing u-boot.img area
(in case u-boot.img size increased, e.g. if new dtbs were added).

This commit conforms with Linux partition table from f6d245b8
("arm: am57xx: Fix Linux boot from eMMC") commit, making things in
uniform way.
Signed-off-by: NSam Protsenko <semen.protsenko@linaro.org>
Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Migrate the option CONFIG_SPL_FRAMEWORK and make this gate most of the
current set of options we have in Kconfig.  We will need to have some
options available for SPL and !SPL_FRAMEWORK so this is important.  In a
few cases we re-order existing options so that we have less escapes from
the SPL_FRAMEWORK guard.
Signed-off-by: NTom Rini <trini@konsulko.com>

The option CONFIG_SPL_MMC_MINIMAL is unused in code, drop it.
Signed-off-by: NTom Rini <trini@konsulko.com>

Add CONFIG_DYNAMIC_CRC_TABLE to am335x_evm_defconfig to reduce the
size of the image.
Signed-off-by: NFaiz Abbas <faiz_abbas@ti.com>

Add CONFIG prefix to DYNAMIC_CRC_TABLE and implement it in
Kconfig.
Signed-off-by: NFaiz Abbas <faiz_abbas@ti.com>

ISO and EFI partition configs in SPL are selected by default.
However, they are not being used.

Therefore, remove ISO and EFI partition support in SPL.
Signed-off-by: NFaiz Abbas <faiz_abbas@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

When this config is enabled, <asm/arch/boot0.h> is included,
but the Kconfig help says this should be a define
(ARM_SOC_BOOT0_HOOK).

The code for this in arch/arm/lib/vectors.s was changed on
01/02/2017 with commit ce62e57f ("ARM: boot0 hook: remove macro,
include whole header file").
Signed-off-by: NSimon Goldschmidt <sgoldschmidt@de.pepperl-fuchs.com>

Commit 6808ef9a ("move booti_setup to arch/arm/lig/image.c")
not only moved the code, but also replaced a tab with 4 spaces
to break the Linux coding style.

Restore tab indentation.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: NBin Chen <bin.chen@linaro.org>

With commit 6808ef9a ("move booti_setup to arch/arm/lig/image.c"),
images->ep has not been set at this point.

Fixes: 6808ef9a ("move booti_setup to arch/arm/lig/image.c")
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: NBin Chen <bin.chen@linaro.org>

Provide description for struct efi_driver_ops.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

%s/Indentiies/Identifies/g
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Signed-off-by: NSimon Goldschmidt <sgoldschmidt@de.pepperl-fuchs.com>

This driver is no longer used on any supported platform in U-Boot and
there is no interest in maintaining it further from people that have
used it historically.

Cc: Simon Glass <sjg@chromium.org>
Cc: Michal Simek <michal.simek@xilinx.com>
c: Alexey Brodkin <alexey.brodkin@gmail.com>
Signed-off-by: NTom Rini <trini@konsulko.com>
Acked-by: NMichal Simek <michal.simek@xilinx.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

Signed-off-by: NTuomas Tynkkynen <tuomas@tuxera.com>

This allows running tests on emulated KC705 board with DC233C xtensa
core. It expects to find conf.xtfpga_qemu in the uboot-test-hooks.
Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>

Remove CONFIG_BOOT_RETRY_TIME as it doesn't do much good and enable
CONFIG_HUSH_PARSER in xtfpga_defconfig.
Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>

xtensa toolchains are core-specific, so give full toolchain name and
download corresponding prebuilt toolchain from the github release.
Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>