- 20 Apr, 2016 13 commits
-
-
git://git.denx.de/u-boot-socfpgaTom Rini authored
-
Stefan Roese authored
This enables full ethernet usage, including U-Boot to write the board specific MAC address (ethaddr) into the DT blob before passing it to Linux. Without this, the ethaddr is not detected in U-Boot at all, resulting in this error upon bootup: ... Model: EBV SOCrates Net: Error: ethernet@ff702000 address not set. No ethernet found. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Stefan Roese authored
Fix a small typo in some of the SoCFPGA dts files that has spread via copy-and-paste. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
The code uses a lot of signed numbers, which ended up in variables of unsigned type, which resulted in all sorts of underflows. This in turn caused incorrect calibration on certain boards. Moreover, repair the readout of the DQ delay, which was being pulled from wrong register. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
Just staticize global variables in sequencer, since there is no point in having these symbols available outside of the DDR code. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
Originally, the DLEVEL selects the debug level within the sequencer code, but only displays the messages on that particular debug level. Tweak the handling such that for particular debug level, debug messages on that level and lower are displayed. This allows better regulation of debug message verbosity. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
This one last set of delay configuration registers was not properly zeroed out originally, fix it and zero them out. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
There is no point in resetting the ODT setting if the write test failed, since the code will always retry the calibration and thus reconfigure the ODT anyway OR the code will fail calibration and halt. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
Every invocation of the scc_mgr_set_dqs_en_delay_all_ranks() is followed by SCC manager update. Moreover, only this function triggers the SCC manager update internally. Thus, remove the internal invocation to avoid triggering the update twice. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
The hi address bitfield in the protection rule must be set to the last address in the region which the rule represents. The behavior is now in-line with code generated by Quartus 15.1 . Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
The code should be setting registers to zero, not one register to value. Swap the order of arguments to correct the behavior. The behavior is now in-line with code generated by Quartus 15.1 . Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
In the most unlikely case the DQS tracking was to be disabled, make sure we do not errornously re-enable it. Note that DQS tracking is enabled on all systems observed thus far. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
Marek Vasut authored
The bit 22 is in fact DQS tracking enable bit (dqstrken) and there is a macro for this bit already, so use it. Signed-off-by:
Marek Vasut <marex@denx.de> Cc: Dinh Nguyen <dinguyen@opensource.altera.com> Cc: Chin Liang See <clsee@altera.com>
-
- 19 Apr, 2016 2 commits
-
-
git://git.denx.de/u-boot-mipsTom Rini authored
-
Purna Chandra Mandal authored
MIPS arch do not update 'reg' property of /memory node. As a result Linux bootup will not work unless board.dts file contains right /memory offset-size information or board implements required memory fixup. Fixing by renaming (unused) _arch_fixup_memory_node_ to _arch_fixup_fdt_ in arch/mips/lib/bootm.c inline with ARM arch. Signed-off-by:
Purna Chandra Mandal <purna.mandal@microchip.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
- 18 Apr, 2016 25 commits
-
-
Robert P. J. Day authored
Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca>
-
Stephen Warren authored
The current code in ARMv8's lowlevel_init() skips the per-CPU GIC initialization ifndef CONFIG_ARMV8_MULTIENTRY. However, the per-CPU init should always occur; it's just the one-time init that should only happen on the master. Once this consideration is taken into account, the only difference between the paths when CONFIG_ARMV8_MULTIENTRY is undefined/defined is the use of branch_if_slave. Naively, any unified code would need to invoke this conditionally upon ifdef CONFIG_ARMV8_MULTIENTRY. However, branch_if_slave already checks CONFIG_ARMV8_MULTIENTRY and does nothing if it isn't defined, so we don't even need that ifdef at the call site. Reported-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by:
Stephen Warren <swarren@nvidia.com> Reviewed-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Akshay Bhat authored
As of commit 69e173eb, CONFIG_OF_LIBFDT needs to be selected in defconfig instead of board specific header file. Hence enable CONFIG_OF_LIBFDT in defconfig. Signed-off-by:
Akshay Bhat <akshay.bhat@timesys.com>
-
Alexander Graf authored
When there is no $fdtfile variable set, we still have a good chance that on 32bit arm the fdtfile really is just called $soc-$board.dtb. Enable the exports for $soc and $board in our distr defaults and make use of them in the efi boot script. Reported-by:
Andreas Faerber <afaerber@suse.de> Reported-by:
Stephen Warren <swarren@wwwdotorg.org> Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Andreas Färber <afaerber@suse.de>
-
Alexander Graf authored
The bootefi cmd today fetches its device tree pointer from either the location appointed by "fdt addr" with a fallback to the U-Boot control fdt. This integration is unusual for U-Boot and diverges from the way we usually handle parameters to boot commands. So let's pass the fdt directly into the bootefi command instead and move the control fdt logic into the distro boot script. Signed-off-by:
Alexander Graf <agraf@suse.de> Acked-by:
Stephen Warren <swarren@wwwdotorg.org> Reviewed-by:
Andreas Färber <afaerber@suse.de>
-
Tom Rini authored
Give a valid value here as well to allow things which want CONFIG_ENV_VARS_UBOOT_CONFIG to build Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Robert P. J. Day authored
Apparently, all "dave"-related vendor content was removed in commit 5344cc1a; remove remaining directory board/dave/, which consists solely of board/dave/common/flash.c. Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca>
-
Tang Yuantian authored
Ensure data the following sata command used is flushed out of dcache and written to physical memory or timeout error may happen. Signed-off-by:
Tang Yuantian <yuantian.tang@nxp.com>
-
Stephen Warren authored
dm_serial_ops.pending should return the number of characters, not just a valid C Boolean integer value. The existing code does already does this, but only as an accident since BCM283X_MU_LSR_RX_READY happens to be BIT(0). Enhance the code to be more explicit about the values it returns. Suggested-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Stephen Warren <swarren@wwwdotorg.org>
-
Robert P. J. Day authored
Clean up the ext4 README file. Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca>
-
Robert P. J. Day authored
Signed-off-by:
Robert P. J. Day <rpjday@crashcourse.ca>
-
Andreas Färber authored
Some variables for the distro boot commands were missing, using some custom name instead. Rename them. Cc: Mateusz Kulikowski <mateusz.kulikowski@gmail.com> Signed-off-by:
Andreas Färber <afaerber@suse.de>
-
Andreas Färber authored
jetson-tk1 has 2 GB of RAM at 0x80000000, causing gd->ram_top to be zero. Handle this by either avoiding ram_top or by using the same type as ram_top to reverse the overflow effect. Cc: Alexander Graf <agraf@suse.de> Signed-off-by:
Andreas Färber <afaerber@suse.de> Reviewed-by:
Alexander Graf <agraf@suse.de>
-
Lokesh Vutla authored
commit 62c5674e ("omap: SPL boot devices cleanup and completion") cleans up the boot device ids for amx3xx soc. But mistakenly updates wrong device IDs for AM43xx USB. Fixing the same here. Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Lokesh Vutla authored
NAND is not yet enabled on all Keystone2 platforms. So enabled CMD_NAND in the respective defconfigs only if available. Reported-by:
Nishanth Menon <nm@ti.com> Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Lokesh Vutla authored
Not all Keystone2 devices has AEMIF NAND controller. So adding Kconfig entry for CONFIG_TI_AEMIF and enabling it in respective defconfigs on platforms with AEMIF controller. Reported-by:
Nishanth Menon <nm@ti.com> Signed-off-by:
Lokesh Vutla <lokeshvutla@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
If get_dev_addr fails it will return FDT_ADDR_T_NONE and: >>> "priv->usid == 4294967295U" is always false regardless of the values of its operands. This occurs as the logical operand of if. Cc: Mateusz Kulikowski <mateusz.kulikowski@gmail.com> Reported-by: Coverity (CID: 143914) Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
If get_dev_addr fails it will return FDT_ADDR_T_NONE and: >>> "priv->pid == 4294967295U" is always false regardless of the values of its operands. This occurs as the logical operand of if. Cc: Mateusz Kulikowski <mateusz.kulikowski@gmail.com> Reported-by: Coverity (CID: 143913) Signed-off-by:
Tom Rini <trini@konsulko.com>
-
angelo@sysam.it authored
fix 19/48 broken board compilations, due to a now too smal 16-bit relative jump Signed-off-by:
Angelo Dureghello <angelo@sysam.it> Acked-by:
Marek Vasut <marex@denx.de> Acked-by:
Heiko Schocher <hs@denx.de>
-
Eric Nelson authored
Call blk_dwrite to ensure that the block cache is notified if enabled and remove build breakage when CONFIG_BLK is enabled. Signed-off-by:
Eric Nelson <eric@nelint.com> Reviewed-by:
Stephen Warren <swarren@nvidia.com>
-
Alexander Graf authored
The EFI memory map does not need to be in a strict order, but 32bit grub2 does expect it to be ascending. If it's not, it may try to allocate memory inside the U-Boot data memory region. We already sort the memory map in descending order, so let's just reverse it when we pass it to a payload. Signed-off-by:
Alexander Graf <agraf@suse.de> Tested-by:
Andreas Färber <afaerber@suse.de>
-
Alexander Graf authored
The uEFI spec doesn't dictate where the device tree should live at, but legacy 32bit ARM grub2 has some assumptions that it may stay at its place when it's already loaded by the firmware. So let's put it somewhere where Linux that comes after would happily find it - around the recommended 128MB line. Signed-off-by:
Alexander Graf <agraf@suse.de> Tested-by:
Andreas Färber <afaerber@suse.de>
-
Alexander Graf authored
The cache line flush helpers only work properly when they get aligned start and end addresses. Round our flush range to cache line size. It's safe because we're guaranteed to flush within a single page which has the same cache attributes. Reported-by:
Marek Vasut <marex@denx.de> Signed-off-by:
Alexander Graf <agraf@suse.de> Reviewed-by:
Andreas Färber <afaerber@suse.de> Tested-by:
Andreas Färber <afaerber@suse.de>
-
Mateusz Kulikowski authored
Add missing define to board header file. Signed-off-by:
Mateusz Kulikowski <mateusz.kulikowski@gmail.com> Acked-by:
Marek Vasut <marex@denx.de> Reviewed-by:
Andreas Färber <afaerber@suse.de>
-
Alexander Graf authored
When the user did not pass any device tree or the boot script didn't find any, let's use the system device tree as last resort to get something the payload (Linux) may understand. This means that on systems that use the same device tree for U-Boot and Linux we can just share it and there's no need to manually provide a device tree in the target image. While at it, also copy and pad the device tree by 64kb to give us space for modifications. Signed-off-by:
Alexander Graf <agraf@suse.de> Tested-by:
Andreas Färber <afaerber@suse.de>
-