- 16 10月, 2015 1 次提交
-
-
- 15 10月, 2015 9 次提交
-
-
由 Fabio Estevam 提交于
PCI driver currently hangs on mx6qp. Toggle the reset bit with the appropriate timings to fix the issue. Based on the FSL kernel driver implementation. Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com> Acked-by: NStefano Babic <sbabic@denx.de>
-
由 Thierry Reding 提交于
Initialize all GICD_IGROUPRn registers and set up GICC_CTLR to enable interrupts to the primary CPU. This fixes issues seen after booting a Linux kernel from U-Boot. Suggested-by: NMarc Zyngier <marc.zyngier@arm.com> Suggested-by: NMark Rutland <mark.rutland@arm.com> Cc: Albert Aribaud <albert.u.boot@aribaud.net> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: NThierry Reding <treding@nvidia.com>
-
由 Thierry Reding 提交于
For EL3 and EL2, the documentation says that bits 31 and 23 are reserved but should be written as 1. For EL1, only bit 23 is not reserved, so only write bit 31 as 1. Cc: Albert Aribaud <albert.u.boot@aribaud.net> Cc: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: NThierry Reding <treding@nvidia.com>
-
-
由 Masahiro Yamada 提交于
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
-
由 Thierry Reding 提交于
Use the inner shareable attribute for memory, which makes more sense considering that this code is called when caches are being enabled. Cc: Albert Aribaud <albert.u.boot@aribaud.net> Cc: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: NThierry Reding <treding@nvidia.com>
-
由 Stefan Agner 提交于
Currently, the device tree relocation is disabled, likely to keep some DDR3 RAM at the end for Cortex-M4 firmwares. This can be archived using bootm_size, which limits the image processing range of the boot commands. Move the device tree standard load address to a higher address which aligns better with what we are doing on other boards. Signed-off-by: NStefan Agner <stefan@agner.ch> Acked-by: NOtavio Salvador <otavio@ossystems.com.br>
-
由 Fabio Estevam 提交于
Commit 3f353cec ("vf610: refactor DDRMC code") changed the original bstlen field from 3 to 0. Restore the original value for proper behaviour. Based on the patch from Anthony Felice <tony.felice@timesys.com> for the vf610twr board. Reported-by: NStefan Agner <stefan@agner.ch> Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
-
由 Stefan Agner 提交于
This resyncs the driver changes with the Linux version of the driver. The driver received some feedback in the LKML and got recently acceppted, the latest version can be found here: https://lkml.org/lkml/2015/9/2/678 Notable changes are: - On ECC error, reread OOB and count bit flips in OOB too. If flipped bits are below threshold, also return an empty OOB buffer. - Return the amount of bit flips in vf610_nfc_read_page. - Use endianness aware vf610_nfc_read to read ECC status. - Do not enable IDLE IRQ (since we do not operate with an interrupt service routine). - Use type safe struct for buffer variants (vf610_nfc_alt_buf). - Renamed variables in struct vf610_nfc (column and page_sz) to reflect better what they really representing. The U-Boot version currently does not support RAW NAND write when using the HW ECC engine. Signed-off-by: NBhuvanchandra DV <bhuvanchandra.dv@toradex.com> Signed-off-by: NStefan Agner <stefan@agner.ch> Tested-by: NAlbert ARIBAUD (3ADEV) <albert.aribaud@3adev.fr> Tested-by: NStefan Agner <stefan@agner.ch> Acked-by: NScott Wood <scottwood@freescale.com>
-
- 14 10月, 2015 1 次提交
-
-
由 Albert ARIBAUD 提交于
-
- 13 10月, 2015 3 次提交
-
-
-
由 Fabio Estevam 提交于
Since commit 623d96e8("imx: wdog: correct wcr register settings") issuing a 'reset' command causes the system to hang. Unlike i.MX and Vybrid, the watchdog controller on LS102x is big-endian. This means that the watchdog on LS1021 has been working by accident as it does not use the big-endian accessors in drivers/watchdog/imx_watchdog.c. Commit 623d96e8("imx: wdog: correct wcr register settings") only revelead the endianness problem on LS102x. In order to fix the reset hang, introduce a reset_cpu() implementation that is specific for ls102x, which accesses the watchdog WCR register in big-endian format. All that is required to reset LS102x is to clear the SRS bit. This approach is a temporary workaround to avoid a regression for LS102x in the 2015.10 release. The proper fix is to make the watchdog driver endian-aware, so that it can work for i.MX, Vybrid and LS102x. Reported-by: NSinan Akman <sinan@writeme.com> Tested-by: NSinan Akman <sinan@writeme.com> Reviewed-by: NWolfgang Denk <wd@denx.de> Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
-
由 Fabio Estevam 提交于
Create fsl_wdog.h to store the watchdog registers and bit fields. This can be useful when accesses to the watchdog block are made from other parts, such as arch/arm/ cpu code. Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>
-
- 12 10月, 2015 26 次提交
-
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Ludger Dreier 提交于
The changes in ed6a5d4f unintentionally broke support for reading the environment saved to eeprom back. To correct this the crc-check and decision on which environment to use is now moved to env_relocate_spec. This is done for both the "redundant env" and the "single env" case. Signed-off-by: NLudger Dreier <ludger.dreier@keymile.com>
-
由 Albert ARIBAUD (3ADEV) 提交于
MTD partitioning in current pcm052 configuration is inconsistent. Fix it across MTDPARTS_DEFAULT, CONFIG_EXTRA_ENV_SETTINGS, and CONFIG_ENV_OFFSET[_REDUND]. Signed-off-by: NAlbert ARIBAUD (3ADEV) <albert.aribaud@3adev.fr>
-
由 Tom Rini 提交于
With the changes in 7a3e70cf we now get read(2) behavior so trying to read 2MB with 1MB left in the file results in 1MB read and a warning. We update the test logic here to make sure we read back 1MB as expected. This change however changes the overall summary as while EXT4 continues to not have offset support the test now fails when expected to pass rather than fails when expected to fail (and we report that as pass). Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Vladimir Zapolskiy 提交于
Execution branches on feedback mode are swapped, this has no effect if default direct mode is on (then p_div is equal to 1 and Fout equals to Fcco), that's why the problem remained unnoticed for a long time. Signed-off-by: NVladimir Zapolskiy <vz@mleia.com>
-
由 Vladimir Zapolskiy 提交于
According to ARM PrimeCell PL175 documentation WAIT_OEN config value is defined without any additional clocks added to the value set by a client, the change fixes the wrong interface to WAIT_OEN config. The change also touches a single user of LPC32xx EMC and corrects configured "output enable delay" value on its side according to the changed interface. No functional change intended. Signed-off-by: NVladimir Zapolskiy <vz@mleia.com>
-
由 Ezequiel García 提交于
Messages on corrected bit-flips are not really useful, as bit-flips are perfectly normal. Let's avoid cluttering the console and make them debug. Signed-off-by: NEzequiel Garcia <ezequiel@vanguardiasur.com.ar>
-
由 Vagrant Cascadian 提交于
When building with SOURCE_DATE_EPOCH set, avoid use of mktime in default_image.c, which converts the timestamp into localtime. This causes variation based on timezone when building u-boot.img and u-boot-sunxi-with-spl.bin targets. Signed-off-by: NVagrant Cascadian <vagrant@debian.org> Tested-by: NPaul Kocialkowski <contact@paulk.fr> Acked-by: NPaul Kocialkowski <contact@paulk.fr>
-
由 Tom Rini 提交于
In 2dd46328 the check for where a ramdisk is found on an Android image was got moved into the "normal" loop here, causing people to have to pass the kernel address in the ramdisk address location in order to have Android boot still. This changed previous behavior so perform a check early in the function to see if we have an Android image and if so use that as where to look for the ramdisk (which is what the rest of the code here expects). We allow for this to still be overridden with an explicit ramdisk address to be passed as normal. Cc: Rob Herring <robh@kernel.org> Reported-by: NPaul Kocialkowski <contact@paulk.fr> Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
Try and make it clear that -D will replace all arguments passed to dtc and is not appending them. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Ian Campbell 提交于
We run 4 Arndale boards in our automated test framework, they have been running quite happily for quite some time using a Debian Wheezy userspace. However when upgrading to a Debian Jessie we started seeing frequent segmentation faults from gcc when building the kernel, to the extent that it is unable to successfully build the kernel twice in a row, and often fails on the first attempt. Searching around I found https://bugs.launchpad.net/arndale/+bug/1081417 which pointed towards http://www.spinics.net/lists/kvm-arm/msg03723.html and CPU Errata 773022 and 774769. This errata needs to be applied to all processors in an SMP system, meaning that the usual strategy of applying them in arch/arm/cpu/armv7/start.S is not appropriate (since that applies to the boot processor only). Instead we apply these errata in the secure monitor which is code that is traversed by all processors as they are brought up. The net affect on Arndale is that ACTLR changes from 0x40 to 0x2000042. I ran 17 kernel compile iterations overnight with no segfaults. Runtime testing was done on our v2014.10 based branch and forward ported (with only minimal and trivial contextual conflicts) to current master, where it has been build tested only. I suppose in theory these errata apply to any Exynos5250 based boards, but Arndale is the only one I have access to and I have therefore chosen to be conservative and only apply it there. Also, reorder CONFIG_ARM_ERRATA_794072 in README to make the list numerically sorted. Signed-off-by: NIan Campbell <ian.campbell@citrix.com>
-
由 Rob Herring 提交于
If an Android boot image does not contain a ramdisk, make sure rd_len and rd_data are returned to indicate no ramdisk rather than just relying on returning an error. Signed-off-by: NRob Herring <robh@kernel.org>
-
由 Julius Werner 提交于
This patch adds support for LZ4-compressed FIT image contents. This algorithm has a slightly worse compression ration than LZO while being nearly twice as fast to decompress. When loading images from a fast storage medium this usually results in a boot time win. Sandbox-tested only since I don't have a U-Boot development system set up right now. The code was imported unchanged from coreboot where it's proven to work, though. I'm mostly interested in getting this recognized by mkImage for use in a downstream project. Signed-off-by: NJulius Werner <jwerner@chromium.org> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Stefan Roese 提交于
This platform has not gone into production. So lets remove it. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
-
由 Stefan Roese 提交于
Add CONFIG_SYS_GENERIC_BOARD to lwmon5.h and CONFIG_DISPLAY_BOARDINFO to Kconfig file. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
-
由 Stefan Roese 提交于
This reverts commit 8fe11b89. I'll add support to lwmon5 in the next patch and will remove support for the broken lcd4_lwmon5 as well. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
-
由 Benoît Thébaudeau 提交于
Overwriting an empty file not created by U-Boot did not work, and it could even corrupt the FAT. Moreover, creating empty files or emptying existing files allocated a cluster, which is not standard. Fix this by always keeping empty files clusterless as specified by Microsoft (the start cluster must be set to 0 in the directory entry in that case), and by supporting overwriting such files. Signed-off-by: NBenoît Thébaudeau <benoit@wsystem.com>
-
由 Benoît Thébaudeau 提交于
Signed-off-by: NBenoît Thébaudeau <benoit@wsystem.com>
-
由 Benoît Thébaudeau 提交于
curclust was used instead of newclust in the debug() calls and in one CHECK_CLUST() call, which could skip a failure case. Signed-off-by: NBenoît Thébaudeau <benoit@wsystem.com>
-
由 Benoît Thébaudeau 提交于
set_contents() had uselessly split calls to set_cluster(). Merge these calls, which removes some cases of set_cluster() being called with a size of zero. Signed-off-by: NBenoît Thébaudeau <benoit@wsystem.com>
-
由 Benoît Thébaudeau 提交于
set_cluster() was using a temporary buffer without enforcing its alignment for DMA and cache. Moreover, it did not check the alignment of the passed buffer, which can come directly from applicative code or from the user. This could cause random data corruption, which has been observed on i.MX25 writing to an SD card. Fix this by only passing ARCH_DMA_MINALIGN-aligned buffers to disk_write(), which requires the introduction of a buffer bouncing mechanism for the misaligned buffers passed to set_cluster(). By the way, improve the handling of the corresponding return values from disk_write(): - print them with debug() in case of error, - consider that there is an error is disk_write() returns a smaller block count than the requested one, not only if its return value is negative. After this change, set_cluster() and get_cluster() are almost symmetrical. Signed-off-by: NBenoît Thébaudeau <benoit@wsystem.com>
-
由 Igor Grinberg 提交于
CONFIG_TWL4030_POWER is a boolean define variable. It is either defined or not defined and should not have a value assigned to it. Remove the value. Signed-off-by: NIgor Grinberg <grinberg@compulab.co.il>
-
由 Ryan Harkin 提交于
This patch changes the default "root=" parameter to "/dev/sda2". Many linux based distros use /dev/sda1 for their boot partition; this is often not a rootfs that can be used by the "root=" parameter. Linaro images use /dev/sda1 as a boot partition, although this of a different nature to a distro image. Linaro uses /dev/sda2 for the rootfs partition. Signed-off-by: NRyan Harkin <ryan.harkin@linaro.org> Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
-
由 Ryan Harkin 提交于
The latest Juno firmware stores the files in NOR flash as "norkern" for kernel binary, "board.dtb" for the device tree binary. The "old" firmware used the name "Image" for the kernel binary and "juno" for the device tree binary. Rather than just change the default U-Boot configuration to use the new names, breaking users with the old firmware, attempt to load the default filename first. If that fails, attempt to load the alternate filename. I've echo'd that we are loading the alternate file to counter the output from "afs load" shown if the first load attempt fails. For example, I see output like this on my Juno board when it's configured the with the "old" firmware: image "norkern" not found in flash Loading Image instead of norkern loaded region 0 from 08500000 to 80000000, 00AB6318 bytes image "board.dtb" not found in flash Loading juno instead of board.dtb loaded region 0 from 0A000000 to 83000000, 00003188 bytes Signed-off-by: NRyan Harkin <ryan.harkin@linaro.org> Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
-
由 Ryan Harkin 提交于
Some OS images require an initrd on Juno. If the file ramdisk.img exists in NOR flash, then we load it and pass the address to the kernel. Otherwise, we pass the "-" parameter as before. Signed-off-by: NRyan Harkin <ryan.harkin@linaro.org> Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
-
由 Ryan Harkin 提交于
Change the load_image so that it returns success or failure of the command (using CMD_RET_SUCCESS or CMD_RET_FAILURE). This way, hush scripts can optionally load different files depending upon the system configuration. A simple example: if afs load ${kernel_name} ${kernel_addr}; then echo loaded; else echo \ not loaded; fi Signed-off-by: NRyan Harkin <ryan.harkin@linaro.org> Reviewed-by: NLinus Walleij <linus.walleij@linaro.org>
-