u-boot.git/include/configs, branch v2018.01

imx: initialize and use generic timer on i.MX 6UL/ULL

2018-01-08T16:33:06+00:00

The i.MX 6UL/ULL feature a Cortex-A7 CPU which suppor the ARM
generic timer. This change makes use of the ARM generic timer in
U-Boot.

This is crucial to make the ARM generic timers usable in Linux since
timer_init() initalizes the system counter module, which is necessary
to use the generic timers CP15 registers.

Signed-off-by: Stefan Agner 
Reviewed-by: Fabio Estevam

imx: move CONFIG_SYSCOUNTER_TIMER to Kconfig

2018-01-08T16:33:06+00:00

Signed-off-by: Stefan Agner 
Reviewed-by: Fabio Estevam

mx6ull: Handle the CONFIG_MX6ULL cases correctly

2018-01-04T15:29:04+00:00

Since commit 051ba9e082f7 ("Kconfig: mx6ull: Deselect MX6UL from
CONFIG_MX6ULL") CONFIG_MX6ULL does not select CONFIG_MX6UL anymore, so
take this into consideration in all the checks for CONFIG_MX6UL.

This fixes a boot regression.

Reported-by: Stefan Agner 
Signed-off-by: Fabio Estevam 
Reviewed-by: Stefan Agner 
Tested-by: Breno Lima 
Tested-by: Peng Fan 
Reviewed-by: Stefano Babic 
Tested-by: Jörg Krause

ARM: imx: cm_fx6: env: don't run boot scripts twice

2018-01-03T13:29:04+00:00

Boot scripts located in the root directory of the first partition of
USB, mmc, and SATA drives are executed twice: first by the distro boot
command and then by the legacy boot command. This may have weird side
effects if those scripts only change or extend the environment
(including parts of the boot command itself).

Removing the script execution from the legacy boot command has its own
caveats. For instance, the distro boot command may execute the boot.scr
on the mmc drive, then the boot.scr on the SATA drive, before the
legacy boot command actually boots from the mmc drive. However, the
current behavior would only execute the boot.scr once more before the
actual boot, but it does not prevent the script located on the SATA
drive from being executed, and thus, both scripts from being mixed up.

Considering that the legacy boot command is only in place to boot old
(standard) installations, let's go with the resolution having less
custom code and remove the script execution from the legacy boot
command.

Signed-off-by: Christopher Spinrath 
Reviewed-by: Fabio Estevam

ARM: imx: cm_fx6: env: support distro boot command

2018-01-03T13:28:49+00:00

The current default environment of the cm_fx6 is not suitable for
booting modern distributions.

Instead of extending the custom environment, let's use the distro
boot command, which has been developed for precisely this use case.

If the distro boot command fails, fall back to the old behavior
(except for USB drives where the old behaviour is completely covered
by the distro boot command). That way it is still possible to create
"rescue SD cards" for old installations (e.g. if one messes up the
on-flash environment).

Signed-off-by: Christopher Spinrath 
Reviewed-by: Fabio Estevam

ARM: imx: cm_fx6: env: use standard variables

2018-01-03T13:27:12+00:00

In preparation for supporting the distro boot command, introduce the
standard variables for specifying load addresses, which are documented
in README and doc/README.distro, and replace the custom variables
used so far with them.

Since the current address layout disregards an address for an initramfs,
also switch to the load addresses used and proven by other imx6 boards
(e.g. the wandboard and nitrogen6x), instead of going on with our own
way.

Signed-off-by: Christopher Spinrath 
Reviewed-by: Fabio Estevam

mx6: Add board mx6memcal for use in validating DDR

2018-01-03T12:58:51+00:00

This is a virtual "board" that uses configuration files and
Kconfig to define the memory layout used by a real board during
the board bring-up process.

It generates an SPL image that can be loaded using imx_usb or
SB_LOADER.exe.

When run, it will generate a set of calibration constants for
use in either or both a DCD configuration file for boards that
use u-boot.imx or struct mx6_mmdc_calibration for boards that
boot via SPL.

In essence, it is a configurable, open-source variant of the
Freescale ddr-stress tool.

	https://community.nxp.com/docs/DOC-105652

File mx6memcal_defconfig configures the board for use with
mx6sabresd or mx6qsabreauto.

Signed-off-by: Eric Nelson 
Signed-off-by: Fabio Estevam

ARM: dts: omap3-evm: Enable DM and devicetree for TMDSEVM{3530, 3730}

2018-01-01T14:04:19+00:00

This commit updates the configuration files needed to support OF_CONTROL
on the OMAP3 EVM baseboard.

Additionally:
- CONFIG_SYS_THUMB_BUILD is enabled
- CONFIG_SPL_ENV_SUPPORT is enabled

Tested using GCC 7.2.0 [--with-float=hard --with-mode=thumb].

Signed-off-by: Derald D. Woods

ARM: omap3: evm: Do not relocate FDT address

2018-01-01T14:04:19+00:00

This commit keeps the 'fdtaddr' as provided by DEFAULT_LINUX_BOOT_ENV.

Signed-off-by: Derald D. Woods

Merge git://git.denx.de/u-boot-imx

2017-12-29T14:27:04+00:00