- 13 3月, 2015 4 次提交
-
-
由 Nishanth Menon 提交于
621766: Under a specific set of conditions, executing a sequence of NEON or vfp load instructions can cause processor deadlock Impacts: Every Cortex-A8 processors with revision lower than r2p1 Work around: Set L1NEON to 1 Based on ARM errata Document revision 20.0 (13 Nov 2010) Signed-off-by: NNishanth Menon <nm@ti.com> Tested-by: NMatt Porter <mporter@konsulko.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Nishanth Menon 提交于
430973: Stale prediction on replaced inter working branch causes Cortex-A8 to execute in the wrong ARM/Thumb state Impacts: Every Cortex-A8 processors with revision lower than r2p1 Work around: Set IBE to 1 Based on ARM errata Document revision 20.0 (13 Nov 2010) Signed-off-by: NNishanth Menon <nm@ti.com> Tested-by: NMatt Porter <mporter@konsulko.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Nishanth Menon 提交于
454179: Stale prediction may inhibit target address misprediction on next predicted taken branch Impacts: Every Cortex-A8 processors with revision lower than r2p1 Work around: Set IBE and disable branch size mispredict to 1 Also provide a hook for SoC specific handling to take place if needed. Based on ARM errata Document revision 20.0 (13 Nov 2010) Signed-off-by: NNishanth Menon <nm@ti.com> Tested-by: NMatt Porter <mporter@konsulko.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Nishanth Menon 提交于
Add workaround for Cortex-A15 ARM erratum 798870 which says "If back-to-back speculative cache line fills (fill A and fill B) are issued from the L1 data cache of a CPU to the L2 cache, the second request (fill B) is then cancelled, and the second request would have detected a hazard against a recent write or eviction (write B) to the same cache line as fill B then the L2 logic might deadlock." Implementations for SoC families such as Exynos, OMAP5/DRA7 etc will be widely different. Every SoC has slightly different manner of setting up access to L2ACLR and similar registers since the Secure Monitor handling of Secure Monitor Call(smc) is diverse. Hence an weak function is introduced which may be overriden to implement SoC specific accessor implementation. Based on ARM errata Document revision 18.0 (22 Nov 2013) Signed-off-by: NNishanth Menon <nm@ti.com> Tested-by: NMatt Porter <mporter@konsulko.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 06 3月, 2015 1 次提交
-
-
由 Masahiro Yamada 提交于
All the DM-related configuration options are described in Kconfig helps. They should not be duplicated in README. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
- 05 3月, 2015 2 次提交
-
-
由 Simon Glass 提交于
At present SPL uses a single stack, either CONFIG_SPL_STACK or CONFIG_SYS_INIT_SP_ADDR. Since some SPL features (such as MMC and environment) require a lot of stack, some boards set CONFIG_SPL_STACK to point into SDRAM. They then set up SDRAM very early, before board_init_f(), so that the larger stack can be used. This is an abuse of lowlevel_init(). That function should only be used for essential start-up code which cannot be delayed. An example of a valid use is when only part of the SPL code is visible/executable, and the SoC must be set up so that board_init_f() can be reached. It should not be used for SDRAM init, console init, etc. Add a CONFIG_SPL_STACK_R option, which allows the stack to be moved to a new address before board_init_r() is called in SPL. The expected SPL flow (for CONFIG_SPL_FRAMEWORK) is documented in the README. Signed-off-by: NSimon Glass <sjg@chromium.org> For version 1: Acked-by: NAlbert ARIBAUD <albert.u.boot@aribaud.net> Reviewed-by: NStefan Roese <sr@denx.de> Tested-by: NBo Shen <voice.shen@atmel.com> Acked-by: NBo Shen <voice.shen@atmel.com> Acked-by: NHeiko Schocher <hs@denx.de> Tested-by: NHeiko Schocher <hs@denx.de> Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Stephen Warren 提交于
When the CPU is in non-secure (NS) mode (when running U-Boot under a secure monitor), certain actions cannot be taken, since they would need to write to secure-only registers. One example is configuring the ARM architectural timer's CNTFRQ register. We could support this in one of two ways: 1) Compile twice, once for secure mode (in which case anything goes) and once for non-secure mode (in which case certain actions are disabled). This complicates things, since everyone needs to keep track of different U-Boot binaries for different situations. 2) Detect NS mode at run-time, and optionally skip any impossible actions. This has the advantage of a single U-Boot binary working in all cases. (2) is not possible on ARM in general, since there's no architectural way to detect secure-vs-non-secure. However, there is a Tegra-specific way to detect this. This patches uses that feature to detect secure vs. NS mode on Tegra, and uses that to: * Skip the ARM arch timer initialization. * Set/clear an environment variable so that boot scripts can take different action depending on which mode the CPU is in. This might be something like: if CPU is secure: load secure monitor code into RAM. boot secure monitor. secure monitor will restart (a new copy of) U-Boot in NS mode. else: execute normal boot process Signed-off-by: NStephen Warren <swarren@nvidia.com> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
- 26 2月, 2015 1 次提交
-
-
由 gaurav rana 提交于
Currently only normal hashing is supported using hardware acceleration. Added support for progressive hashing using hardware. Signed-off-by: NRuchika Gupta <ruchika.gupta@freescale.com> Signed-off-by: NGaurav Rana <gaurav.rana@freescale.com> CC: Simon Glass <sjg@chromium.org> Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
- 25 2月, 2015 1 次提交
-
-
由 York Sun 提交于
Add sync of refresh for multiple DDR controllers. DDRC initialization needs to complete first. Code is re-ordered to keep refresh close. Signed-off-by: NYork Sun <yorksun@freescale.com>
-
- 17 2月, 2015 1 次提交
-
-
由 Christian Gmeiner 提交于
A SoC like the i.MX6 supports more then one i2c bus. In oder to be able to use the eeprom command add a new define to specify the i2c bus to use. If CONFIG_SYS_I2C_EEPROM_BUS is not defined there is no functional change, else a call to i2c_set_bus_num(..) is done before calling i2c_read(..) and i2c_write(..). Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com> Acked-by: NStefano Babic <sbabic@denx.de>
-
- 08 2月, 2015 1 次提交
-
-
由 Heiko Schocher 提交于
make the HW WDT timeout configurable through the define CONFIG_AT91_HW_WDT_TIMEOUT. Signed-off-by: NHeiko Schocher <hs@denx.de>
-
- 30 1月, 2015 2 次提交
-
-
由 Ruchika Gupta 提交于
Modify rsa_verify to use the rsa driver of DM library .The tools will continue to use the same RSA sw library. CONFIG_RSA is now dependent on CONFIG_DM. All configurations which enable FIT based signatures have been modified to enable CONFIG_DM by default. Signed-off-by: NRuchika Gupta <ruchika.gupta@freescale.com> CC: Simon Glass <sjg@chromium.org> Acked-by: NSimon Glass <sjg@chromium.org>
-
Some image types, like "KeyStone GP", do not have magic numbers to distinguish them from other image types. Thus, the automatic image type discovery does not work correctly. This patch also fix some integer type mismatches. Signed-off-by: NGuilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>
-
- 16 1月, 2015 1 次提交
-
-
由 Masahiro Yamada 提交于
All the 74xx_7xx boards are still non-generic boards: P3G4, ZUMA, ppmc7xx, ELPPC, mpc7448hpc2 Acked-by: NMarek Vasut <marex@denx.de> Acked-by: NStefan Roese <sr@denx.de> Acked-by: NYork Sun <yorksun@freescale.com> Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Nye Liu <nyet@zumanetworks.com> Cc: Roy Zang <tie-fei.zang@freescale.com>
-
- 06 1月, 2015 2 次提交
-
-
由 Jeremiah Mahler 提交于
Fix various spelling and grammatical errors in the README. Signed-off-by: NJeremiah Mahler <jmmahler@gmail.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
All the MPC824X boards are still non-generic boards: A3000, CPC45, CU824, eXalion, MVBLUE, MUSENKI, Sandpoint824x, utx8245 Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Josef Wagner <Wagner@Microsys.de> Cc: Torsten Demke <torsten.demke@fci.com> Cc: Jim Thompson <jim@musenki.com> Cc: Greg Allen <gallen@arlut.utexas.edu>
-
- 19 12月, 2014 2 次提交
-
-
由 Thierry Reding 提交于
Implement an API that can be used by drivers to allocate memory from a pool that is mapped uncached. This is useful if drivers would otherwise need to do extensive cache maintenance (or explicitly maintaining the cache isn't safe). The API is protected using the new CONFIG_SYS_NONCACHED_MEMORY setting. Boards can set this to the size to be used for the non-cached area. The area will typically be right below the malloc() area, but architectures should take care of aligning the beginning and end of the area to honor any mapping restrictions. Architectures must also ensure that mappings established for this area do not overlap with the malloc() area (which should remain cached for improved performance). While the API is currently only implemented for ARM v7, it should be generic enough to allow other architectures to implement it as well. Signed-off-by: NThierry Reding <treding@nvidia.com> Signed-off-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NTom Warren <twarren@nvidia.com>
-
由 Thierry Reding 提交于
Implement an API that can be used by drivers to allocate memory from a pool that is mapped uncached. This is useful if drivers would otherwise need to do extensive cache maintenance (or explicitly maintaining the cache isn't safe). The API is protected using the new CONFIG_SYS_NONCACHED_MEMORY setting. Boards can set this to the size to be used for the non-cached area. The area will typically be right below the malloc() area, but architectures should take care of aligning the beginning and end of the area to honor any mapping restrictions. Architectures must also ensure that mappings established for this area do not overlap with the malloc() area (which should remain cached for improved performance). While the API is currently only implemented for ARM v7, it should be generic enough to allow other architectures to implement it as well. Signed-off-by: NThierry Reding <treding@nvidia.com> Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 18 12月, 2014 1 次提交
-
-
由 Steve Rae 提交于
Implement a feature to allow fastboot to write the downloaded image to the space reserved for the Protective MBR and the Primary GUID Partition Table. Additionally, prepare and write the Backup GUID Partition Table. Signed-off-by: NSteve Rae <srae@broadcom.com> Tested-by: NLukasz Majewski <l.majewski@samsung.com> [Test HW: Exynos4412 - Trats2]
-
- 08 12月, 2014 1 次提交
-
-
由 Paul Kocialkowski 提交于
Raw images of U-Boot can be stored inside MMC partitions, so it makes sense to read the partition table, looking for a partition number instead of using a fixed sector address. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@ti.com> [trini: Only add mmc_load_image_raw_partition() when CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION to avoid warning, add missing conversion in spl_mmc_load_image()] Signed-off-by: NTom Rini <trini@ti.com>
-
- 06 12月, 2014 1 次提交
-
-
由 Prabhakar Kushwaha 提交于
When device is configured to load RCW from NAND flash IFC_A[16:31] are driven low after RCW loading. Hence Devices connected on IFC_CS[1:7] and using IFC_A[16:31] lines are not accessible. Workaround is already in-place. Put the errata number to adhere errata handling framework. Signed-off-by: NPrabhakar Kushwaha <prabhakar@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
- 05 12月, 2014 1 次提交
-
-
由 Paul Kocialkowski 提交于
CONFIG_SYS_MMC_SD_FS_BOOT_PARTITION ought to be called CONFIG_SYS_MMCSD_FS_BOOT_PARTITION to keep it consistent with other config options such as: CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR. In addition, it is not related to raw mode booting but to fs mode instead. Signed-off-by: NPaul Kocialkowski <contact@paulk.fr> Reviewed-by: NTom Rini <trini@ti.com>
-
- 23 11月, 2014 2 次提交
-
-
由 Masahiro Yamada 提交于
The README file states that the macros beginning with "CONFIG_SYS_" depend on the hardware etc. and should not be meddled with if you do not what you're doing. We have already screwed up with this policy; we have given the prefix "CONFIG_SYS_" to many user-selectable configurations. Here, "CONFIG_SYS_HUSH_PARSER" is one of them. Users can enable it if they want to use a more powerful command line parser, or disable it if they only need a simple one. This commit attempts to rename CONFIG_SYS_HUSH_PARSER to CONFIG_HUSH_PARSER and move it to Kconfig. Every board maintainer is expected to enable CONFIG_HUSH_PARSER (= add "CONFIG_HUSH_PARSER=y" to his defconfig file) and remove "#define CONFIG_SYS_HUSH_PARSER" from his header file. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Christian Gmeiner 提交于
Some filesystems have a UUID stored in its superblock. To allow using root=UUID=... for the kernel command line we need a way to read-out the filesystem UUID. changes rfc -> v1: - make the environment variable an option parameter. If not given, the UUID is printed out. If given, it is stored in the env variable. - corrected typos - return error codes changes v1 -> v2: - fix return code of do_fs_uuid(..) - document do_fs_uuid(..) - implement fs_uuid_unsuported(..) be more consistent with the way other optional functionality works changes v2 -> v3: - change ext4fs_uuid(..) to make use of #if .. #else .. #endif construct to get rid of unreachable code Hit any key to stop autoboot: 0 => fsuuid fsuuid - Look up a filesystem UUID Usage: fsuuid <interface> <dev>:<part> - print filesystem UUID fsuuid <interface> <dev>:<part> <varname> - set environment variable to filesystem UUID => fsuuid mmc 0:1 d9f9fc05-45ae-4a36-a616-fccce0e4f887 => fsuuid mmc 0:2 eb3db83c-7b28-499f-95ce-9e0bb21cda81 => fsuuid mmc 0:1 uuid1 => fsuuid mmc 0:2 uuid2 => printenv uuid1 uuid1=d9f9fc05-45ae-4a36-a616-fccce0e4f887 => printenv uuid2 uuid2=eb3db83c-7b28-499f-95ce-9e0bb21cda81 => Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com> Acked-by: NStephen Warren <swarren@nvidia.com>
-
- 21 11月, 2014 2 次提交
-
-
由 Simon Glass 提交于
Add documentation for the various driver model options that are now available. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Add an additional function for adding information to the device tree before booting. This permits additions which are not board-specific. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NAnatolij Gustschin <agust@denx.de> Reviewed-by: NTom Rini <trini@ti.com>
-
- 17 11月, 2014 1 次提交
-
-
由 Heiko Schocher 提交于
enable to boot only a raw u-boot.bin image from nand with the CONFIG_SPL_NAND_RAW_ONLY define. This option saves space on boards where spl space is low. Signed-off-by: NHeiko Schocher <hs@denx.de> Reviewed-by: NAndreas Bießmann <andreas.devel@googlemail.com> Reviewed-by: NBo Shen <voice.shen@atmel.com> Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>
-
- 08 11月, 2014 1 次提交
-
-
由 Timo Ketola 提交于
Correct environment variable for output directory is KBUILD_OUTPUT. Signed-off-by: NTimo Ketola <timo@exertus.fi>
-
- 28 10月, 2014 1 次提交
-
-
由 Guillaume GARDET 提交于
Update documentation according to the EXT SPL support patch set. Signed-off-by: NGuillaume GARDET <guillaume.gardet@free.fr> Cc: Tom Rini <trini@ti.com>
-
- 27 10月, 2014 1 次提交
-
-
由 Gabe Black 提交于
There's a definition in stdint.h (provided by gcc) which will be more correct if available. Define CONFIG_USE_STDINT to use this feature, or USE_STDINT=1 on the 'make' commmand. This adjusts the settings for x86 and sandbox, with both have 64-bit options. Signed-off-by: NGabe Black <gabeblack@google.com> Reviewed-by: NGabe Black <gabeblack@chromium.org> Tested-by: NGabe Black <gabeblack@chromium.org> Reviewed-by: NBill Richardson <wfrichar@google.com> Rewritten to be an option, since stdint.h is often available only in glibc. Changed to preserve a clear boundary between stdint and non-stdint Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 24 10月, 2014 1 次提交
-
-
由 Masahiro Yamada 提交于
CONFIG_SYS_HZ is always defined as 1000 in config_fallbacks.h (but some boards still have redundant definitions). This commit moves the definition and the document in README to Kconfig. Since lib/Kconfig can assure that CONFIG_SYS_HZ is 1000, the sanity check in lib/time.c should be removed. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by: NMarek Vasut <marex@denx.de>
-
- 23 10月, 2014 3 次提交
-
-
由 Stefan Roese 提交于
Add target to build it automatically upon "make" / MAKEALL. This can/should be set by board / cpu specific headers if a special U-Boot image is required for this SoC / board. E.g. used by Marvell Armada XP to automatically build the u-boot.kwb target. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Simon Glass 提交于
It does seem to work (tested on link), so update the docs. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Oleksandr Tymoshenko 提交于
This is the USB host controller used on the Altera SoCFPGA and Raspbery Pi. This code has three checkpatch warnings, but to make sure it stays at least readable and clear, these are not fixed. These bugs are in the USB request handling combinatorial logic, so any abstracting of those is out of question. Tested on DENX MCV (Altera SoCFPGA 5CSFXC6C6U23C8N) and RPi B+ (BCM2835). Signed-off-by: NOleksandr Tymoshenko <gonzo@bluezbox.com> Signed-off-by: NStephen Warren <swarren@wwwdotorg.org> Signed-off-by: NMarek Vasut <marex@denx.de> Cc: Chin Liang See <clsee@altera.com> Cc: Dinh Nguyen <dinguyen@altera.com> Acked-by: NPavel Machek <pavel@denx.de> Cc: Vince Bridgers <vbridger@altera.com> Tested-by: NDinh Nguyen <dinguyen@opensource.altera.com>
-
- 17 10月, 2014 1 次提交
-
-
由 Ruchika Gupta 提交于
SEC registers can be of type Little Endian or big Endian depending upon Freescale SoC. Here SoC defines the register type of SEC IP. So update acessor functions with common SEC acessor functions to take care both type of endianness. Signed-off-by: NRuchika Gupta <ruchika.gupta@freescale.com> Reviewed-by: NYork Sun <yorksun@freescale.com>
-
- 25 9月, 2014 2 次提交
-
-
由 York Sun 提交于
U-boot has been initializing DDR for the main memory. The presumption is the memory stays as a big continuous block, either linear or interleaved. This change is to support putting some DDR controllers to separated space without counting into main memory. The standalone memory controller could use different number of DIMM slots. Signed-off-by: NYork Sun <yorksun@freescale.com>
-
由 Steve Rae 提交于
- implement 'fastboot flash' for eMMC devices Signed-off-by: NSteve Rae <srae@broadcom.com> Acked-by: NLukasz Majewski <l.majewski@samsung.com> Reviewed-by: NMarek Vasut <marex@denx.de>
-
- 24 9月, 2014 1 次提交
-
-
由 Simon Glass 提交于
A merge error ended up repeating a similar sentence twice. Fix it. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 22 9月, 2014 1 次提交
-
-
- Use _defconfig instead of _config, but still _config is working. - Corrected README.sandbox path in ./README Signed-off-by: NJagannadha Sutradharudu Teki <jaganna@gmail.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
- 30 8月, 2014 1 次提交
-
-
由 Tom Rini 提交于
The default format for arm64 Linux kernels is the "Image" format, described in Documentation/arm64/booting.txt. This, along with an optional gzip compression on top is all that is generated by default. The Image format has a magic number within the header for verification, a text_offset where the Image must be run from, an image_size that includes the BSS and reserved fields. This does not support automatic detection of a gzip compressed image. Signed-off-by: NTom Rini <trini@ti.com>
-