17 Feb, 2018
4 commits
-
With multiple environments, the 'get_char' callback for env
drivers does not really make sense any more because it is
only supported by two drivers (eeprom and nvram).To restore single character loading for these drivers,
override 'env_get_char_spec'.Signed-off-by: Simon Goldschmidt
Acked-by: Maxime Ripard -
Commit 7d714a24d725 ("env: Support multiple environments") added
static variable env_load_location. When saving environmental
variables, this variable is presumed to have the value set before.
In case the value was set before relocation and U-Boot runs from a
NOR flash, this variable wasn't writable. This causes failure when
saving the environment. To save this location, global data must be
used instead.Signed-off-by: York Sun
CC: Maxime Ripard
16 Feb, 2018
1 commit
15 Feb, 2018
21 commits
-
Commit 958d55f26ce ("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: Alexander Graf
-
Kconfig should only 'select' features that are required for an arch.
Standard features that can be disabled without breaking board support
should use 'imply' instead, to allow users to disable it.These options are changed for mach-socfpga:
- DM_SPI & DM_SPI_FLASH: only required with QSPI support enabled
- SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION: the boot rom supports a
partitionless mode also, where SPL is located at address 0
- HW_WATCHDOG: while all mainline board defconfigs use it, U-Boot
should still work without it.Signed-off-by: Simon Goldschmidt
-
All Socfpga boards from ./include/configs/socfpga_* define
CONFIG_HW_WATCHDOG.
To ease CONFIG_HW_WATCHDOG conversion to Kconfig select it in
config ARCH_SOCFPGA (arch/arm/Kconfig) section.Signed-off-by: Lukasz Majewski
Signed-off-by: Simon Goldschmidt -
This patch adds "spi-flash" to the compatible list of the qspi flash
chip for all socfpga boards. This is required to make qspi work on
these boards on top of the recent fixes. Without the "spi-flash"
compatible string for the flash chip, the speed cannot be read and a
speed of 0Hz is used (which results in a divide-by-zero on these
boards).Signed-off-by: Simon Goldschmidt
-
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: Alexey Brodkin
-
board_usb_init()/_cleanup() should be in board files and don't have
a place in the xhci-omap driver. Weak versions for
board_usb_init()/_cleanup() already exist in common/usb.c
(for host mode) and drivers/usb/gadget/g_dnl.c (for gadget mode).Therefore, remove init and cleanup functions from xhci-omap and
implement them in the board files.Signed-off-by: Faiz Abbas
Reviewed-by: Marek Vasut
Reviewed-by: Bin Meng -
For some reason from day one we used to have both CONFIG_DWC2_UTMI_WIDTH
mentioned in dwc2.h and in scripts/config_whitelist.txt but never really used
and CONFIG_DWC2_UTMI_PHY_WIDTH used in real code in dwc2.c (but never
defined).Moreover even though CONFIG_DWC2_UTMI_WIDTH might be either 8 or 16
depending on hardware (and the same is said in a comment for it in
dwc2.h) but then 8 is hardcoded in the header leaving no ability to
override this value in board's configuration.Signed-off-by: Alexey Brodkin
Cc: Marek Vasut -
This converts the following to Kconfig:
CONFIG_SYS_BOOTCOUNT_SINGLEWORDSigned-off-by: Lukasz Majewski
Tested-by: Alex Kiernan
Reviewed-by: Ian Ray -
This converts the following to Kconfig:
CONFIG_BOOTCOUNT_LIMITSigned-off-by: Lukasz Majewski
Tested-by: Alex Kiernan
Reviewed-by: Hannes Schmelzer
Acked-by: Hannes Schmelzer -
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini
-
Upon further review, not all code authors are in favour of this change.
This reverts commit ee3556bcafbb05e59aabdc31368984e76acaabc4.Signed-off-by: Tom Rini
-
With commit 9bd76b807636 ("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: 9bd76b807636 ("spl: make CONFIG_OF_EMBED pass dts through fdtgrep")
Reported-by: Lokesh Vutla
Signed-off-by: Simon Goldschmidt
Reviewed-by: Lokesh Vutla -
Configuration option CMD_SCSI should be placed in the same submenu as
CMD_SATA and CMD_MMC.Signed-off-by: Heinrich Schuchardt
-
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: Andre Heider
-
The single argument `--noheader' is expecting isn't taken from getopt
parsing, but instead from the remaining argv arguments.Signed-off-by: Alex Kiernan
-
>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 f6d245b8c56c
("arm: am57xx: Fix Linux boot from eMMC") commit, making things in
uniform way.Signed-off-by: Sam Protsenko
Reviewed-by: Lokesh Vutla
Reviewed-by: Tom Rini -
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: Tom Rini
-
The option CONFIG_SPL_MMC_MINIMAL is unused in code, drop it.
Signed-off-by: Tom Rini
-
Add CONFIG_DYNAMIC_CRC_TABLE to am335x_evm_defconfig to reduce the
size of the image.Signed-off-by: Faiz Abbas
-
Add CONFIG prefix to DYNAMIC_CRC_TABLE and implement it in
Kconfig.Signed-off-by: Faiz Abbas
-
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: Faiz Abbas
Reviewed-by: Tom Rini
14 Feb, 2018
14 commits
-
When this config is enabled, 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 ce62e57fc571 ("ARM: boot0 hook: remove macro,
include whole header file").Signed-off-by: Simon Goldschmidt
-
Commit 6808ef9ac2a6 ("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: Masahiro Yamada
Reviewed-by: Bin Chen -
With commit 6808ef9ac2a6 ("move booti_setup to arch/arm/lig/image.c"),
images->ep has not been set at this point.Fixes: 6808ef9ac2a6 ("move booti_setup to arch/arm/lig/image.c")
Signed-off-by: Masahiro Yamada
Reviewed-by: Bin Chen -
Provide description for struct efi_driver_ops.
Signed-off-by: Heinrich Schuchardt
-
%s/Indentiies/Identifies/g
Signed-off-by: Heinrich Schuchardt
-
Signed-off-by: Simon Goldschmidt
-
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
Cc: Michal Simek
c: Alexey Brodkin
Signed-off-by: Tom Rini
Acked-by: Michal Simek -
Signed-off-by: Tuomas Tynkkynen
-
Signed-off-by: Tuomas Tynkkynen
-
Signed-off-by: Tuomas Tynkkynen
-
Signed-off-by: Tuomas Tynkkynen
-
Signed-off-by: Tuomas Tynkkynen
-
Signed-off-by: Tuomas Tynkkynen
-
Signed-off-by: Tuomas Tynkkynen
