- Nov 29, 2016
-
-
The ipu has two display interfaces. Make the used one a parameter in struct display_info_t instead of using unconditionally DI0. DI0 is the default setting. Signed-off-by:
Max Krummenacher <max.krummenacher@toradex.com> Reviewed-by:
Eric Nelson <eric@nelint.com>
-
If CONFIG_SPL_LIBCOMMON_SUPPORT is not defined there is a lone case statement at the end of the switch leading to a compile error. Remove the offending case statement. | common/spl/spl_mmc.c:339:7: error: label at end of compound statement Signed-off-by:
Max Krummenacher <max.krummenacher@toradex.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Acked-by:
Marek Vasut <marex@denx.de>
-
Check BOOT_CFG2[3:4] to determine which SD/MMC port is selected to boot from. If MMC2 is selected return BOOT_DEVICE_MMC2. In all other cases return BOOT_DEVICE_MMC1, as we do not have corresponding macro for MMC3 and MMC4. Signed-off-by:
Marcin Niestroj <m.niestroj@grinn-global.com>
-
-
Stefan Agner authored
Introduce USB Gadget config option. This allows to combine Makefile entries for SPL_USBETH_SUPPORT and SPL_DFU_SUPPORT. Signed-off-by:
Stefan Agner <stefan.agner@toradex.com> Acked-by:
Lukasz Majewski <l.majewski@samsung.com> Tested-by:
Ravi Babu <ravibabu@ti.com>
-
Stefan Agner authored
The DFU Kconfig menu entries should be part of the SPL Kconfig file. Also avoid using the top level Makefile by moving the config dependent build artifacts to the driver/ and driver/usb/gadget/ Makfiles. With that, DFU can be built again in SPL if CONFIG_SPL_DFU_SUPPORT is enabled. Fixes: 6ad61022 ("usb:gadget: Disallow DFU in SPL for now") Signed-off-by:
Stefan Agner <stefan.agner@toradex.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Acked-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Stefan Agner authored
Some devices (e.g. dra7xx) support loading to RAM using DFU without having direct boot from RAM support. Make sure the linker list does not contain BOOT_DEVICE_RAM if CONFIG_SPL_RAM_DEVICE is not enabled. Fixes: 98136b2f ("spl: Convert spl_ram_load_image() to use linker list") Signed-off-by:
Stefan Agner <stefan.agner@toradex.com> Acked-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Nicolae Rosia authored
The actual define symbol is FAT_ENV_DEVICE_AND_PART Signed-off-by:
Nicolae Rosia <Nicolae_Rosia@Mentor.com>
-
tomas.melin@vaisala.com authored
This fixes the loop delay when using a hw watchdog. In case a watchdog is used that accesses CPU registers, the defined delay of 20us in a tight loop will cause a huge delay in the actual timeout seen. This is caused by the fact that udelay will inheritantly call WATCHDOG_RESET. Together with the omap wdt implementation, the seen timeout increases up to around 30s. This makes the loop very slow and causes long delays when using the modem. Instead, implement the 2 sec loop by using the timer interface to know when to break out of the timeout loop. Watchdog kicking is taken care of by getc(). Signed-off-by:
Tomas Melin <tomas.melin@vaisala.com>
-
Tang Yuantian authored
Commit d97dc8a0 separated the non-command code into its own file which caused variable sata_curr_device can not be set to a correct value. Before commit d97dc8a0, variable sata_curr_device can be set correctly in sata_initialize(). After commit d97dc8a0, sata_initialize() is moved out to its own file. Accordingly, variable sata_curr_device is removed from sata_initialize() too. This caused sata_curr_device never gets a chance to be set properly which prevent other commands from being executed. This patch sets variable sata_curr_device properly. Fixes: d97dc8a0 (dm: sata: Separate the non-command code into its own file) Signed-off-by:
Tang Yuantian <yuantian.tang@nxp.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Nov 28, 2016
-
-
Max Krummenacher authored
commit 183923d3 enforces that the environment must start at an erase block boundary. For block devices the sample fw_env.config does not mandate a erase block size for block devices. A missing setting defaults to the full env size. Depending on the environment location the alignment check now errors out for perfectly legal settings. Fix this by defaulting to the standard blocksize of 0x200 for environments stored in a block device. That keeps the fw_env.config files for block devices working even with that new check. Signed-off-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Andre Przywara authored
The Makefile in tools/ tries to find the "swig" utility by calling "which". If nothing is found in the path, some versions of which will print an error message: $ make clean which: no swig in (/usr/local/bin:/usr/bin:/bin) This does not apply to all version of "which", though: $ echo $0 bash $ type which which is aliased to `type -path' $ which foo <== this version is OK $ /usr/bin/which foo <== this one is chatty /usr/bin/which: no foo in (/usr/local/bin:/usr/bin:/bin) $ sh <== make uses /bin/sh sh-4.3$ which foo <== no alias here which: no foo in (/usr/local/bin:/usr/bin:/bin) This error message is rather pointless in our case, since we just have this very check to care for this. So add stderr redirection to suppress the message. Signed-off-by:
Andre Przywara <andre.przywara@arm.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Andrew F. Davis authored
NFS loading support has been added to the default environment for most boot components, as PMMC and MON loading were added later they did not originally get the NFS commands added, add these now. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Lokesh Vutla <lokeshvutla@ti.com>
-
Andrew F. Davis authored
The config option TARGET_K2x_EVM is set by the k2x defconfigs to pick a board target, but the header configs also set K2x_EVM. This config is redundant, remove it and use TARGET_K2x_EVM everywhere in its place. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Lokesh Vutla <lokeshvutla@ti.com>
-
Stefan Roese authored
This patch fixes the warning about misaligned cache on Armada XP: CACHE: Misaligned operation at range [7ffff000, 7fffffac] Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Valentin Longchamp <valentin.longchamp@keymile.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
mario.six@gdsys.cc authored
Commit c68c62 ("i2c: mvtwsi: Make delay times frequency-dependent") extensively used the ndelay function with a calculated parameter which is dependant on the configured frequency of the I2C bus. If standard speed is employed, the parameter is usually 10000 (10000ns period length for 100kHz frequency). But, since the arm architecture does not implement a proper version of ndelay, the fallback default from include/linux/compat.h is used, which defines every ndelay as udelay(1). This causes problems for slower speeds on arm, since the delay time is now 9us too short for the desired frequency, which leads to random failures of the I2C interface. To remedy this, we implement a proper, parameter-aware ndelay fallback for architectures that don't implement a real ndelay function. Reported-By:
Jason Brown <Jason.brown@apcon.com> To: Tom Rini <trini@konsulko.com> To: Heiko Schocher <hs@denx.de> Signed-off-by:
Mario Six <mario.six@gdsys.cc>
-
Max Krummenacher authored
remove now unused CONFIG_TRDX_PID_XXX Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Acked-by:
Stefan Agner <stefan.agner@toradex.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Marcel Ziswiler authored
Now with the config block handling in place move the U-Boot environment location before the config block at the end of 1st "boot sector" as deployed during production using our downstream BSP. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Marcel Ziswiler authored
With our common code in place actually make use of it across all our modules. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Marcel Ziswiler authored
Add Toradex factory configuration block handling. The config block is a data structure which gets stored to flash during production testing. The structure holds such information as board resp. hardware revision, product ID and serial number which is used as the NIC part of the Ethernet MAC address as well. The config block will be read upon boot by the show_board_info() function, displayed as part of the board information and passed to Linux via device tree or ATAGs. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Marcel Ziswiler authored
Deactivate CONFIG_DISPLAY_BOARDINFO in favour of CONFIG_DISPLAY_BOARDINFO_LATE which also displays on the LCD. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Marcel Ziswiler authored
Make show_board_info() a weak function which allows for custom board specific implementations thereof. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
Marcel Ziswiler authored
Drop CONFIG_CUSTOM_BOARDINFO as it is not Kconfig compliant and anyway not really used anywhere plus the upcoming weak show_board_info() approach seems much superior. This reverts commit a9ad18c9. Signed-off-by:
Marcel Ziswiler <marcel.ziswiler@toradex.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Acked-by:
Max Krummenacher <max.krummenacher@toradex.com>
-
tomas.melin@vaisala.com authored
Image header was checked twice. Signed-off-by:
Tomas Melin <tomas.melin@vaisala.com> Acked-by:
Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
tomas.melin@vaisala.com authored
Add check for FDT_MAGIC, otherwise also legacy images will be loaded as a FIT. With this check in place, the loader works correct both with legacy and FIT images. Signed-off-by:
Tomas Melin <tomas.melin@vaisala.com> Acked-by:
Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Philipp Tomsich authored
To send a parametrized command to the PHY over MDIO, we should write the data first, the trigger the execution by the command register write. Fix the access pattern in our MDIO write routine. Apparently this doesn't really matter with the Realtek PHY on the Pine64, but other PHYs (which require more setup) will choke on the wrong order. [Andre: add commit message] Signed-off-by:
Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Signed-off-by:
Andre Przywara <andre.przywara@arm.com> Acked-by:
Jagan Teki <jagan@openedev.com>
-
FUKAUMI Naoki authored
Add board support for sun8i_r16 Nintendo NES Classic edition. Signed-off-by:
FUKAUMI Naoki <naobsd@gmail.com> [jagan: Add commit message body] Signed-off-by:
Jagan Teki <jagan@openedev.com> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
Boris Brezillon authored
Add the description of the Toshiba TC58NVG2S0H SLC nand to the nand_ids table so we can use the NAND ECC infos and the ONFI timings. Signed-off-by:
Boris Brezillon <boris.brezillon@free-electrons.com> Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com>
-
Hans de Goede authored
And also remove it from scripts/config_whitelist.txt as the Mele_M5_defconfig was the only one defining it. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Ian Campbell <ijc@hellion.org.uk> Reviewed-by:
Jagan Teki <jagan@openedev.com>
-
Emmanuel Vadot authored
Set CONFIG_SYS_MMC_MAX_DEVICE to 4 for sunxi SoC. This define is needed in the API code. Signed-off-by:
Emmanuel Vadot <manu@bidouilliste.com> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com>
-
Yann E. MORIN authored
Currently, USB is forced-enabled for the sunxi familly, and there is no way to disable it. However, USB takes a long time to initiliase, delaying the boot by up to 5 seconds (without any USB device attached!). This is a very long delay, especially in cases where USB booting is not wanted at all, and where the device is expected to boot relatively often (even in production). Change the way the dependencies are handled, by only forcibly selecting USB when CONFIG_DISTRO_DEFAULTS ("defaults suitable for booting general purpose Linux distributions") is set. This option defaults to y for the sunxi familly, so the current default behaviour is kept unchanged. Users interested in boot time and/or size will be able to disable this to further disable USB. With USB disabled, the time spent in U-Boot before handing control to the Linux kernel is about 1s now, down from ~5s (Nanopi Neo, sunxi H3). Signed-off-by:
"Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Ian Campbell <ijc@hellion.org.uk> Cc: Hans De Goede <hdegoede@redhat.com> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com>
-
Jelle van der Waa authored
Use the already available Kconfig option for AHCI. Tested on the BananaPi. Signed-off-by:
Jelle van der Waa <jelle@vdwaa.nl> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
Hans de Goede <hdegoede@redhat.com>
-
- Nov 27, 2016
-
-
Alexander Graf authored
We have all the building blocks now to run arbitrary efi applications in travis. The most important one out there is grub2, so let's add a simple test to verify that grub2 still comes up. Signed-off-by:
Alexander Graf <agraf@suse.de>
-
Alexander Graf authored
Most of the time when running the sleep test in Travis for the integratorcp_cm926ejs target I get errors like this: E assert 2.999901056289673 >= 3 The deviation is tiny, but fails the overall build result. Since the sleep test is not terribly important as gate keeper for travis tests, let's just exclude it for this board. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Alexander Graf authored
Today we can compile a self-contained hello world efi test binary that allows us to quickly verify whether the EFI loader framwork works. We can use that binary outside of the self-contained test case though, by providing it to a to-be-tested system via tftp. This patch separates compilation of the helloworld.efi file from including it in the u-boot binary for "bootefi hello". It also modifies the efi_loader test case to enable travis to pick up the compiled file. Because we're now no longer bloating the resulting u-boot binary, we can enable compilation always, giving us good travis test coverage. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- Nov 26, 2016
-
-
Alexander Graf authored
Now that we have working network tests and a hello world efi application built inside our tree, we can automatically test that efi binary running inside of U-Boot. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Alexander Graf authored
When running in travis-ci, we want to pass environment configuration to the tests. These reside in a path available through PYTHONPATH, so let's define that one to point to the unit test repo. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Alexander Graf authored
Some travis QEMU tests can transfer files between the build directory and the guest U-Boot instance. For that to work, both need to have access to the same directory. This patch puts the current build path into an environment variable, so that the environment generating python scripts can extract it from there and read the respective files. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Alexander Graf authored
The network test currently downloads files at 0MB offset of RAM start. This works for most ARM systems, but x86 has weird memory layout constraints on the first MB of RAM. To not get caught into any of these, let's add a 4MB pad from start of RAM to the default memory offset. Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-