- 09 3月, 2015 4 次提交
-
-
由 Przemyslaw Marczak 提交于
This commit introduces new config: CONFIG_SYS_MALLOC_CLEAR_ON_INIT. This config is an expert option and is enabled by default. The all amount of memory reserved for the malloc, is by default set to zero in mem_malloc_init(). When the malloc reserved memory exceeds few MiB, then the boot process can slow down. So disabling this config, is an expert option to reduce the boot time, and can be disabled by Kconfig. Note: After disable this option, only calloc() will return the pointer to the zeroed memory area. Previously, without this option, the memory pointed to untouched malloc memory region, was filled with zeros. So it means, that code with malloc() calls should be reexamined. Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Przemyslaw Marczak 提交于
For writing files, DFU implementation requires the file buffer with the len at least of file size. For big files it requires the same big buffer. Previously the file buffer was allocated as a static variable, so it was a part of U-Boot .bss section. For 32MiB len of buffer we have 32MiB of additional space, required for this section. The .bss needs to be cleared after the relocation. This introduces an additional boot delay at every start, but usually the dfu feature is not required at the standard boot, so the buffer should be allocated only if required. This patch removes the static allocation of this buffer, and alloc it with memalign after first call of function: - dfu_fill_entity_mmc() and the buffer is freed on dfu_free_entity() call. This was tested on Trats2. A quick test with trace. Boot time from start to main_loop() entry: - ~888ms - before this change (arch memset enabled for .bss clear) - ~464ms - after this change Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Cc: Lukasz Majewski <l.majewski@samsung.com> Cc: Stephen Warren <swarren@nvidia.com> Cc: Pantelis Antoniou <panto@antoniou-consulting.com> Cc: Tom Rini <trini@konsulko.com> Cc: Marek Vasut <marek.vasut@gmail.com>
-
由 Przemyslaw Marczak 提交于
For ARM architecture, enable the CONFIG_USE_ARCH_MEMSET/MEMCPY, will highly increase the memset/memcpy performance. This is able thanks to the ARM multiple register instructions. Unfortunatelly the relocation is done without the cache enabled, so it takes some time, but zeroing the BSS memory takes much more longer, especially for the configs with big static buffers. A quick test confirms, that the boot time improvement after using the arch memcpy for relocation has no significant meaning. The same test confirms that enable the memset for zeroing BSS, reduces the boot time. So this patch enables the arch memset for zeroing the BSS after the relocation process. For ARM boards, this can be enabled in board configs by defining: 'CONFIG_USE_ARCH_MEMSET'. This was tested on Trats2. A quick test with trace. Boot time from start to main_loop() entry: - ~1384ms - before this change - ~888ms - after this change Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Cc: Albert Aribaud <albert.u.boot@aribaud.net> Cc: Tom Rini <trini@konsulko.com>
-
由 Przemyslaw Marczak 提交于
This commit enables the following configs: - CONFIG_USE_ARCH_MEMCPY - CONFIG_USE_ARCH_MEMSET This increases the performance of memcpy/memset and also reduces the boot time. This was tested on Trats2. A quick test with trace. Boot time from start to main_loop() entry: - ~1527ms - before this change (arch memset enabled for .bss clear) - ~1384ms - after this change Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com> Reviewed-by: NSimon Glass <sjg@chromium.org> Cc: Minkyu Kang <mk7.kang@samsung.com> Cc: Akshay Saraswat <akshay.s@samsung.com> Cc: Simon Glass <sjg@chromium.org> Cc: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
-
- 08 3月, 2015 1 次提交
-
-
- 06 3月, 2015 35 次提交
-
-
由 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>
-
由 Masahiro Yamada 提交于
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This strdup() is missing a check. Add it. Signed-off-by: NSimon Glass <sjg@chromium.org> Acked-by: NHeiko Schocher <hs@denx.de>
-
-
-
-
-
由 Masahiro Yamada 提交于
Since commit e02ee254 (kconfig: switch to single .config configuration), the ".*.cmd" files are not correctly created for SPL/TPL. The U-Boot extension code in fixdep, which was introduced to support the multiple .config, must be removed. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Alexey Brodkin 提交于
With limit of 16 symbols very simple device names derived drom device tree description could not be displayed correctly. For example "serial0@0xc0fc1000" will be truncated to sensless "serial0@0xc0fc10" - note dropped tariling zeros. Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com> Cc: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Fabio Estevam 提交于
Currently the usage text for the 'ums' command looks like this: Usage: ums ums <USB_controller> [<devtype>] <devnum> e.g. ums 0 mmc 0 ,so remove the extra 'ums' in the text. Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com> Acked-by: NOtavio Salvador <otavio@ossystems.com.br> Acked-by: NMarek Vasut <marex@denx.de>
-
由 Alexey Brodkin 提交于
In case of global data structure defined as "register volatile" compiler throws an warning about incorrect type used: --->8--- common/board_f.c: In function "board_init_f_r": common/board_f.c:1073:2: warning: passing argument 1 of "&board_init_r +(sizetype)gd->reloc_off" discards "volatile" qualifier from pointer target type [enabled by default] (board_init_r + gd->reloc_off)(gd, gd->relocaddr); ^ common/board_f.c:1073:2: note: expected "struct gd_t *" but argument is of type "volatile struct gd_t *" --->8--- An obvious fix is manual casting to "gd_t *". Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com> Cc: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Alexey Brodkin 提交于
lib/asm-offsets - make GD_RELOCADDR, GD_RELOC_OFF & GD_START_ADDR_SP available for all architectures GD_RELOCADDR, GD_RELOC_OFF & GD_START_ADDR_SP are generic members of global data structure so why don't we allow architectures other than ARM to use it. Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com> Cc: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@ti.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Heiko Schocher 提交于
running "spl export ..." more than once fails with: Trying to execute a command out of order Trying to execute a command out of order Trying to execute a command out of order Trying to execute a command out of order Trying to execute a command out of order Trying to execute a command out of order ERROR prep subcommand failed! Subcommand failed reason is commmit: 35fc84fa: Refactor the bootm command to reduce code duplication It used "state != BOOTM_STATE_START" but state is a bitfield, so check if the bit BOOTM_STATE_START is not set. With this fix, "spl export ..." can called more than once ... Signed-off-by: NHeiko Schocher <hs@denx.de> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Linus Walleij 提交于
This enables the vexpress64 to detect its NOR flash so that we can load kernel etc from it. Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
-
由 Chen Gang 提交于
For some assemblers, they use another character as newline in a macro (e.g. arc uses '`'), so for generic assembly code, need use ASM_NL (a macro) instead of ';' for it. Basically this is the same patch as applied to Linux kernel - http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/include/linux/linkage.h?id=9df62f054406992ce41ec4558fca6a0fa56fffeb but modified a bit to fit in U-Boot. Signed-off-by: NChen Gang <gang.chen.5i5j@gmail.com> Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com> Cc: Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Simon Glass <sjg@chromium.org> Cc: Tom Rini <trini@ti.com>
-
由 Ash Charles 提交于
The 'nandecc sw' command selects a software-based error correction algorithm. By default, this is OMAP_ECC_HAM1_CODE_SW but some platforms use OMAP_ECC_BCH8_CODE_HW_DETECTION_SW as their software-based correction algorithm. Allow a user to be specific e.g. # nandecc sw <hamming|bch8> where 'hamming' is still the default. Note: we don't just use CONFIG_NAND_OMAP_ECCSCHEME as it might be set to a hardware-based ECC scheme---a little strange when the user has requested 'sw' ECC. Signed-off-by: NAsh Charles <ashcharles@gmail.com>
-
由 Michal Sojka 提交于
Commit fb384c47 introduced the use of WAIT0 pin for determining whether the NAND is ready or not. This only works if all NAND chips are connected to WAIT0. If some chips are connected to the other available pin WAIT1, nand_wait() does not really wait and prints a WARN_ON message. This patch allows the board to provide configuration of which chip is connected to which WAITx signal. For example, one can define in include/configs/foo.h: #define CONFIG_NAND_OMAP_GPMC_WSCFG 0,0,1,1 This would mean that chips using to CS0 and 1 are connected to WAIT0 and chips with CS2 and 3 are connected to WAIT1. Signed-off-by: NMichal Sojka <sojka@merica.cz> Acked-by: NStefan Roese <sr@denx.de> Tested-by: NMichal Vokáč <michal.vokac@comap.cz> Cc: Tom Rini <trini@ti.com>
-
由 Przemyslaw Marczak 提交于
After rework of the file system API, the size of ext4 write was missed. This causes printing unreliable write size at the end of the file system write operation. Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com> Cc: Sjoerd Simons <sjoerd.simons@collabora.co.uk> Cc: Lukasz Majewski <l.majewski@samsung.com> Cc: Simon Glass <sjg@chromium.org> Tested-by: NStephen Warren <swarren@nvidia.com>
-
由 Linus Walleij 提交于
This configures the Juno board to enable ethernet using the SMSC9118 ethernet controller found in the board. Tested by TFTP-booting a kernel over ethernet. Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
-
由 Alison Wang 提交于
This patch adds generic board support for MCF547X/8X and MCF5445X. It is based on the patch about common generic board support for M68K architecture sent by Angelo. Signed-off-by: NAlison Wang <alison.wang@freescale.com>
-
由 angelo@sysam.it 提交于
Add generic-board support for the m68k architecture. Signed-off-by: NAngelo Dureghello <angelo@sysam.it>
-
由 angelo@sysam.it 提交于
Add Freescale MCF5307 cpu support. Signed-off-by: NAngelo Dureghello <angelo@sysam.it>
-
由 angelo@sysam.it 提交于
Add Sysam Amcore m68k-based board support. Signed-off-by: NAngelo Dureghello <angelo@sysam.it>
-
由 Gilles Gameiro 提交于
-
由 Albert ARIBAUD \(3ADEV\) 提交于
This patch extends OMAP3 support for AM/DM37xx and introduces the AM3703-based Quipos Cairo board. Signed-off-by: NAlbert ARIBAUD (3ADEV) <albert.aribaud@3adev.fr> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Peter Tyser 提交于
Remove duplicate command names in usage messages to fix issues such as: => help yls yls - yaffs ls Usage: yls yls [-l] dirname Signed-off-by: NPeter Tyser <ptyser@xes-inc.com>
-
由 Hannes Petermaier 提交于
For some cases it is necessary to modify temporaly the bootcommand. This can be done by writing into the Scratchregister a specific value: * 0xCC - modify bootcmd "run netboot" * 0xCD - modify bootcmd "run netscript" * 0xCE - modify bootcmd "run mmcboot" the environment in flash is NOT overwritten. Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
vxWorks needs several parameters which are set by the bootloader und his environment. So we form a vxWorks bootline and pass the result to vxWorks on a predefined address. Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
Due to several changes in the boot-process we do a complete redesign of the default environment. Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
For series testing purpose we need to boot some linux, therefore we enable the needed features - bootz - devicetree Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
The board has been redesigned, therefore we need from now other I/O Pins to mux and handle. Older boards aren't supported from now anymore. Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
remove unnary '#define ETHLED_ORANGE (96+16) /* GPIO3_16 */' Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
Due to several changes of the boot-process we've redesigned the default- environment settings completly. Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
Customer wants to display some logo very quickly after power on, so we support from now loading a compressed bmp.gz to the screen. Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-
由 Hannes Petermaier 提交于
time measurement of u-boot commands is needed very often during development. We add this feature until development is completed. Maybe forever :) Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>
-