- 10 1月, 2018 1 次提交
-
-
由 Chris Packham 提交于
The DB-88F6820-AMC connects ethernet@34000 and ethernet@70000 which are labeled as eth2 and eth0 in armada-38x.dts. The ethernet@30000 (eth1) is not used on the AMC board. This eliminates the following bootup message Device 'ethernet@70000': seq 0 is in use by 'ethernet@34000' Signed-off-by: NChris Packham <judge.packham@gmail.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
- 09 1月, 2018 15 次提交
-
-
由 Miquel Raynal 提交于
Armada pinctrl drivers shall not be compiled without the entire pinctrl framework and thus lack a "depends on" condition, otherwise the driver will simply not be probed. Signed-off-by: NMiquel Raynal <miquel.raynal@free-electrons.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Miquel Raynal 提交于
Until now, Armada 3700 SoCs could not enable the mvneta driver, and thus did not benefit from Ethernet support. Add ARMADA_3700 in the "depends on" list of the MVNETA Kconfig entry. Signed-off-by: NMiquel Raynal <miquel.raynal@free-electrons.com> Acked-by: NJoe Hershberger <joe.hershberger@ni.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Florian Klink 提交于
Signed-off-by: NFlorian Klink <flokli@flokli.de> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Andre Heider 提交于
Signed-off-by: NAndre Heider <a.heider@gmail.com> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Andre Heider 提交于
Signed-off-by: NAndre Heider <a.heider@gmail.com> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Andre Heider 提交于
the values of dt_addr_r/kernel_addr_r/ramdisk_addr_r are taken from the downstream 'u-boot-2017.03-armada-17.10' release. the chosen values of scriptaddr and pxefile_addr_r are below fdt_addr_r, in 1MB steps. Signed-off-by: NAndre Heider <a.heider@gmail.com> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Andre Heider 提交于
Signed-off-by: NAndre Heider <a.heider@gmail.com> Reviewed-by: NKonstantin Porotchkin <kostap@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Konstantin Porotchkin 提交于
Introduce the recovery image download script for usage with Marvell Armada SoC families (excepting 37xx family). Since Marvell BootROM uses a sliding window in UART buffer for detecting escape sequence during the boot, it's easier to interrupt the normal boot flow by sending a long stream of chained escape sequences to the serial port instead of periodically sending a single escape sequence as it is done by kwboot utility. Additional benefit of using this script is the ability to adjust the escape sequence stream length withoiut need for compilation. Signed-off-by: NKonstantin Porotchkin <kostap@marvell.com> Cc: Stefan Roese <sr@denx.de> Cc: Igal Liberman <igall@marvell.com> Signed-off-by: NStefan Roese <sr@denx.de>
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
-
由 Jagan Teki 提交于
It is not much needed to print nand size in SPL during nand boot, and most of nand spl drivers doesn't print the same. Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Jagan Teki 提交于
board/icorem6_rqs/ is forgot to remove while moving common board files together in (sha1: 52aaddd6) "i..MX6: engicam: Add imx6q/imx6ul boards for existing boards" Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
-
由 Stefan Agner 提交于
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: NStefan Agner <stefan.agner@toradex.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Stefan Agner 提交于
Introduce a new config symbol to select the i.MX General Purpose Timer (GPT). Signed-off-by: NStefan Agner <stefan.agner@toradex.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Stefan Agner 提交于
Signed-off-by: NStefan Agner <stefan.agner@toradex.com> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
- 08 1月, 2018 5 次提交
-
-
-
由 Clemens Gruber 提交于
The blob_encap and blob_decap functions were not flushing the dcache before passing data to CAAM/DMA and not invalidating the dcache when getting data back. Therefore, blob encapsulation and decapsulation failed with errors like the following due to data cache incoherency: "40000006: DECO: desc idx 0: Invalid KEY command" To ensure coherency, we require the key_mod, src and dst buffers to be aligned to the cache line size and flush/invalidate the memory regions. The same requirements apply to the job descriptor. Tested on an i.MX6Q board. Reviewed-by: NSumit Garg <sumit.garg@nxp.com> Signed-off-by: NClemens Gruber <clemens.gruber@pqgruber.com>
-
由 Andy Shevchenko 提交于
As defined on reference board followed by Intel Edison a Bluetooth device is attached to HSU0, i.e. PCI 0000:04.1. Describe it in ACPI accordingly. Note, we use BCM2E95 ID here as one most suitable for such device based on the description in commit message of commit 89ab37b489d1 ("Bluetooth: hci_bcm: Add support for BCM2E95 and BCM2E96") in the Linux kernel source tree. Signed-off-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com> Acked-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Andy Shevchenko 提交于
The recent commit 03c4749dd6c7 ("gpio / ACPI: Drop unnecessary ACPI GPIO to Linux GPIO translation") in the Linux kernel reveals the issue we have in ACPI tables here, i.e. we must use hardware numbers for GPIO resources and, taking into consideration that GPIO and pin control are *different* IPs on Intel Tangier, we need to supply numbers properly. Besides that, it improves user experience since the official documentation for Intel Edison board is referring to GPIO hardware numbering scheme. Signed-off-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com> Acked-by: NBin Meng <bmeng.cn@gmail.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Tom Rini 提交于
We only need to compile and link these files when building for full U-Boot. Move them to under cmd/x86/ to make sure they aren't linked in and undiscarded due to u_boot_list_2_cmd_* being included). Cc: Bin Meng <bmeng.cn@gmail.com> Signed-off-by: NTom Rini <trini@konsulko.com> Reviewed-by: NBin Meng <bmeng.cn@gmail.com>
-
- 04 1月, 2018 2 次提交
-
-
由 Fabio Estevam 提交于
Since commit 051ba9e0 ("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: NStefan Agner <stefan@agner.ch> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com> Reviewed-by: NStefan Agner <stefan@agner.ch> Tested-by: NBreno Lima <breno.lima@nxp.com> Tested-by: NPeng Fan <peng.fan@nxp.com> Reviewed-by: NStefano Babic <sbabic@denx.de> Tested-by: NJörg Krause <joerg.krause@embedded.rocks>
-
-
- 03 1月, 2018 10 次提交
-
-
由 Christopher Spinrath 提交于
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: NChristopher Spinrath <christopher.spinrath@rwth-aachen.de> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Christopher Spinrath 提交于
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: NChristopher Spinrath <christopher.spinrath@rwth-aachen.de> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Christopher Spinrath 提交于
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: NChristopher Spinrath <christopher.spinrath@rwth-aachen.de> Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Philipp Tomsich 提交于
The Rockchip-released ATF for the Firefly apparently (i.e. Kever reported this) does not tolerate a FDT being passed as the platform parameter and will run into a hard stop. To work around this limitation in the ATF parameter handling, we enable SPL_ATF_NO_PLATFORM_PARAM (which will force passing NULL for the platform parameters). Note that this only affects this platform, as the ATF releases for the RK3368 and RK3399 have always either ignored the platform parameter (i.e. before the FDT-based parameters were supported) or support receiving a pointer to a FDT. Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Philipp Tomsich 提交于
While we expect to call a pointer to a valid FDT (or NULL) as the platform parameter to an ATF, some ATF versions are not U-Boot aware and have an insufficiently robust (or an overzealour) parameter validation: either way, this may cause a hard-stop with uncooperative ATF versions. This change adds the option to suppress passing a platform parameter and will always pass NULL. Debug output from ATF w/ this option disabled (i.e. default): INFO: plat_param_from_bl2: 0x291450 Debug output from ATF w/ this option enabled: INFO: plat_param_from_bl2: 0 Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
-
由 Eran Matityahu 提交于
commit 20f14714 ("imx: spl: Update NAND bootmode detection bit") broke the NAND bootmode detection by checking if BOOT_CFG1[7:4] == 0x8 for NAND boot mode. This commit essentially reverts it, while using the IMX6_BMODE_* macros that were introduced since. Tables 8-7 & 8-10 from IMX6DQRM say the NAND boot mode selection is done when BOOT_CFG1[7] is 1, but BOOT_CFG1[6:4] is not necessarily 0x0 in this case. Actually, NAND boot mode is when 0x8 <= BOOT_CFG1[7:4] <= 0xf, like it was in the code before. Signed-off-by: NEran Matityahu <eran.m@variscite.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Jagan Teki <jagan@openedev.com> Cc: Tim Harvey <tharvey@gateworks.com>
-
由 Eric Nelson 提交于
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: NEric Nelson <eric@nelint.com> Signed-off-by: NFabio Estevam <fabio.estevam@nxp.com>
-
由 Peng Fan 提交于
The calculation of left space for version string is not correct, should use VIDEO_COLS not VIDEO_LINE_LEN / 2, otherwise we will get larger space than actual have and cause string to overlay logo picture. Also current version string display only supports two lines words at max. This also causes overlay when the LCD pixel column size is not enough. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Tested-by: NAnatolij Gustschin <agust@denx.de>
-
由 Peng Fan 提交于
The clk_set_rate function dereferences the clk pointer without checking whether it is NULL. This may cause problem when clk is NULL. Signed-off-by: NPeng Fan <peng.fan@nxp.com> Signed-off-by: NAnatolij Gustschin <agust@denx.de>
-
由 Philipp Tomsich 提交于
We want to have the same configuration defaults for the RK3368-uQ7 as for the RK3399-Q7: this change reduces the default env-size to 8KiB to ensure that it does not overlap the boot-payload on SD/MMC configurations. References: commit fe529e65 ("rockchip: rk3399-puma: reduce env size to 8kiB") Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
-
- 02 1月, 2018 2 次提交
-
-
由 Neil Armstrong 提交于
Khadas VIM is an Open Source DIY Box manufactured by Shenzhen Wesion NOT 'Tomato' The fix was provided by Khadas Team member 'numbqq'. Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 01 1月, 2018 5 次提交
-
-
-
由 Felix Brack 提交于
The patch replaces the former error() by the new pr_err(). This makes the TPS65910 driver conform to Masahiro's patch 'treewide:replace with error() with pr_err()' introduced October 2017. Signed-off-by: NFelix Brack <fb@ltec.ch> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Sam Protsenko 提交于
Commit b6251db8 ("Kconfig: Introduce USE_BOOTCOMMAND and migrate BOOTCOMMAND") removed CONFIG_BOOTCOMMAND option from include/configs/am335x_evm.h file. But that option wasn't added to defconfig files for BeagleBone Black board. Because of this we can't boot Linux from SD card using just "run bootcmd", getting next error: ** File not found /boot/undefined ** That's because "fdtfile" variable has "undefined" value by default, and "bootcmd" doesn't call "run findfdt" command, which assigns "fdtfile" to correct device tree file for current board name (obtained from EEPROM). So we are forced to either call "run findfdt" command manually, or assign manually "fdtfile=am335x-boneblack.dtb" (e.g. in uEnv.txt file). Bring back CONFIG_BOOTCOMMAND to BBB defconfigs so that we can boot Linux rootfs from SD card automatically without any addition actions. Signed-off-by: NSam Protsenko <semen.protsenko@linaro.org>
-
由 Heinrich Schuchardt 提交于
struct driver_info has no field 'flags'. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Derald D. Woods 提交于
This commit clears 'ethaddr' before calling 'smc911x_initialize' to allow the SROM MAC address to be assigned properly. Signed-off-by: NDerald D. Woods <woods.technical@gmail.com>
-