- 25 9月, 2014 21 次提交
-
-
由 Masahiro Yamada 提交于
Since CONFIG_CMD_CRC32 is defined in config_cmd_defaults.h, it is enabled for all the boards except the ones undefining it explicitly: kwb tseries_mmc tseries_nand tseries_spi vct_platinum_onenand_small vct_platinum_small vct_platinumavc_onenand_small vct_platinumavc_small vct_premium_onenand_small vct_premium_small The default value of this config option should be "y" and "# CONFIG_CMD_CRC32 is not set" should be added for those exceptions. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
CONFIG_CMD_BOOTM is defined in config_cmd_defaults.h which is forcebly included from each board. So, the default value of "config CMD_BOOTM" should be "y". For some boards undefining it (bf506f-ezkit, controlcenterd_TRAILBLA, controlcenterd_TRAILBLAZER_DEVELOP, controlcenterd_TRAILBLAZER), "# CONFIG_CMD_BOOTM is not set" should be added to their defconfig. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
If this option is enabled, the objects under lib/ directory are compiled with speed optimization, not size optimization. (Currently, only used by some Blackfin boards.) Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
This would be useful to start moving various config options. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org> Tested-by: NSimon Glass <sjg@chromium.org>
-
由 Hans de Goede 提交于
Scsi disks need to be probed before we try to access them, otherwise all accesses fail with: ** Bad device size - scsi 0 **. Reported-by: NKarsten Merker <merker@debian.org> Signed-off-by: NHans de Goede <hdegoede@redhat.com> Reviewed-by: NStephen Warren <swarren@nvidia.com> Tested-by: NKarsten Merker <merker@debian.org>
-
由 Masahiro Yamada 提交于
Since commit ddaf5c8f (patman: RunPipe() should not pipe stdout/stderr unless asked), Patman spits lots of "Invalid MAINTAINERS address: '-'" error messages for patches with global changes. It takes too long for Patman to process them. Anyway, "M: -" does not carry any important information. Rather, it is just like a place holder in case of assigning a new board maintainer. Let's comment out. This commit can be reproduced by the following command: find . -name MAINTAINERS | xargs sed -i -e '/^M:[[:blank:]]*-$/s/^/#/' Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Masahiro Yamada 提交于
The "S: Orphan" in MAINTAINERS means that the maintainer in the "M:" field is unreachable (i.e. the email address is not working). (Refer to the definition of "Orphan" adopted in U-Boot in the log of commit 31f1b654, "boards.cfg: move boards with invalid emails to Orphan") For patch files adding global changes, scripts/get_maintainer.pl adds bunch of such invalid email addresses, which results in tons of annoying bounce emails. This commit can be reproduced by the following command: find . -name MAINTAINERS | xargs sed -i -e ' /^M:[[:blank:]]/ { N /S:[[:blank:]]Orphan/s/^/#/ } ' Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Masahiro Yamada 提交于
We are still keeping invalid email addressed in MAINTAINERS because they carry information. The problem is that scripts/get_maintainer.pl adds emails in the "M:" field including invalid ones. We want to comment out invalid email addresses in MAINTAINERS to prevent scripts/get_maintainer.pl from picking them up. On the other hand, we want to collect them for boards.cfg to know the last known maintainer of each board. This commit adjusts tools/genboardscfg.py to parse also the commented "M:" fields, which is useful for the next commit. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
-
由 Simon Glass 提交于
This performs a command, then repeats it, and checks that the repeat happens. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
These cause U-Boot to print a list of available commands. It doesn't break the test, but it is best to remove them from the output. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This is not supported properly on sandbox, and interferes with running tests, since when a test script is piped in, some commands will call ctrlc() which will drop characters from the test script. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This was lost sometime in the Kbuild conversion. Add it back. Check that the trace test now passes: $ ./test/trace/test-trace.sh Simple trace test / sanity check using sandbox /tmp/filemHKPGw Build sandbox O=sandbox FTRACE=1 GEN /home/sjg/c/src/third_party/u-boot/files/sandbox/Makefile Configuring for sandbox board... Check results Test passed Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Pavel Machek 提交于
Cleanup disk/part.c Signed-off-by: NPavel Machek <pavel@denx.de>
-
由 Masahiro Yamada 提交于
Each CPU of PowerPC has its default linker script under the CPU directory, except mpc8xx. Every mpc8xx board has its own linker script under the board directory, resulting in lots of duplication of linker scripts. I notice eight mpc8xx boards have the same linker script. We can decrease the number of linker scripts by putting a single default linker script, arch/powerpc/cpu/mpc8xx/u-boot.lds. Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Cc: Wolfgang Denk <wd@denx.de> Acked-by: NStefan Roese <sr@denx.de>
-
由 Marcel Ziswiler 提交于
Fix the following build error in case CONFIG_E1000_NO_NVM is enabled: CC drivers/net/e1000.o drivers/net/e1000.c: In function ‘e1000_initialize’: drivers/net/e1000.c:5365:5: error: ‘struct e1000_hw’ has no member named ‘eeprom_semaphore_present’ make[1]: *** [drivers/net/e1000.o] Error 1 make: *** [drivers/net] Error 2 Acked-by: NMarek Vasut <marex@denx.de>
-
由 Thomas Petazzoni 提交于
When building the U-Boot tools for non-ELF platforms (such as Blackfin FLAT), since commit 79fc0c5f ("tools/env: cross-compile fw_printenv without setting HOSTCC"), the build fails because it tries to strip a FLAT binary, which does not make sense. This commit solves this by changing the stripping logic in tools/env/Makefile to be similar to the one in tools/Makefile. This logic continues to apply strip to the final binary, but does not abort the build if it fails, and does the stripping in place on the final binary. This allows the logic to work fine if stripping doesn't work, as it leaves the final binary untouched. Signed-off-by: NThomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Sonic Zhang <sonic.zhang@analog.com> Reviewed-by: NMasahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by: NSonic Zhang <sonic.zhang@analog.com>
-
由 Steve Rae 提交于
- add capability to "fastboot flash" with sparse format images Signed-off-by: NSteve Rae <srae@broadcom.com> Acked-by: NLukasz Majewski <l.majewski@samsung.com>
-
由 Steve Rae 提交于
- update static function - additional debugging statements - update "fastboot command" information - add missing include file - update spelling Signed-off-by: NSteve Rae <srae@broadcom.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>
-
由 Steve Rae 提交于
- add support for 'fastboot flash' command for eMMC devices Signed-off-by: NSteve Rae <srae@broadcom.com>
-
由 Zhiqiang Hou 提交于
Enable the Extend address to support SPI flash more than 16MB. Signed-off-by: NHou Zhiqiang <B48286@freescale.com> Reviewed-by: NJagannadha Sutradharudu Teki <jagannadh.teki@gmail.com>
-
- 24 9月, 2014 14 次提交
-
-
由 Stefan Roese 提交于
Signed-off-by: NStefan Roese <sr@denx.de> Cc: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Acked-by: NPrafulla Wadaskar <prafulla@marvell.com> Tested-by: NLuka Perkov <luka@openwrt.org> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Stefan Roese 提交于
Signed-off-by: NStefan Roese <sr@denx.de> Acked-by: NPrafulla Wadaskar <prafulla@marvell.com> Tested-by: NLuka Perkov <luka@openwrt.org> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Stefan Roese 提交于
This patch introduces the clrsetbits_le32() accessor functions in the kirkwood SPI driver. Note that it also includes a fix: - writel(~KWSPI_CSN_ACT | KWSPI_SMEMRDY, &spireg->ctrl); + writel(KWSPI_SMEMRDY, &spireg->ctrl); Here the bit KWSPI_CSN_ACT (0x1) should have been cleared. Instead 0xfffffffe is written into this control register. This is the main reason to use the clrsetbits() functions now. As they make clearing bits much less error prone. Additionally KWSPI_IRQUNMASK is not used in spi_cs_activate() and spi_cs_deactivate() any more. Its the wrong macro but has the same value as the correct one (KWSPI_CSN_ACT). This is in preparation for use of this driver on the Marvell Armada XP platform as well. Signed-off-by: NStefan Roese <sr@denx.de> Acked-by: NPrafulla Wadaskar <prafulla@marvell.com> Tested-by: NLuka Perkov <luka@openwrt.org> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Stefan Roese 提交于
Signed-off-by: NStefan Roese <sr@denx.de> Tested-by: NLuka Perkov <luka@openwrt.org> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Stefan Roese 提交于
Add ID for this Numonix / STMicro chip. Tested on Marvell DB-78460-BP board. Signed-off-by: NStefan Roese <sr@denx.de> Tested-by: NLuka Perkov <luka@openwrt.org> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Nikita Kiryanov 提交于
Currently, CONFIG_SPL_SPI_* #defines are used for controlling SPI boot in SPL. These #defines do not allow the user to select SPI mode for the SPI flash (there's no CONFIG_SPL_SPI_MODE, so the SPI mode is hardcoded in spi_spl_load.c), and duplicate information already provided by CONFIG_SF_DEFAULT_* #defines. Kill CONFIG_SPL_SPI_*, and use CONFIG_SF_DEFAULT_* instead. Cc: Tom Rini <trini@ti.com> Cc: Marek Vasut <marex@denx.de> Cc: Sudhakar Rajashekhara <sudhakar.raj@ti.com> Cc: Lokesh Vutla <lokeshvutla@ti.com> Cc: Vitaly Andrianov <vitalya@ti.com> Cc: Lars Poeschel <poeschel@lemonage.de> Cc: Bo Shen <voice.shen@atmel.com> Cc: Hannes Petermaier <hannes.petermaier@br-automation.com> Cc: Michal Simek <monstr@monstr.eu> Acked-by: NMarek Vasut <marex@denx.de> Signed-off-by: NNikita Kiryanov <nikita@compulab.co.il> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Nikita Kiryanov 提交于
MXC SPI driver has a feature whereas a GPIO line can be used to force CS high across multiple transactions. This is set up by embedding the GPIO information in the CS value: cs = (cs | gpio << 8) This merge of cs and gpio data into one value breaks the sf probe command: if the use of gpio is required, invoking "sf probe <cs>" will not work, because the CS argument doesn't have the GPIO information in it. Instead, the user must use "sf probe <cs | gpio << 8>". For example, if bank 2 gpio 30 is used to force cs high on cs 0, bus 0, then instead of typing "sf probe 0" the user now must type "sf probe 15872". This is inconsistent with the description of the sf probe command, and forces the user to be aware of implementaiton details. Fix this by introducing a new board function: board_spi_cs_gpio(), which will accept a naked CS value, and provide the driver with the relevant GPIO, if one is necessary. Cc: Eric Nelson <eric.nelson@boundarydevices.com> Cc: Eric Benard <eric@eukrea.com> Cc: Fabio Estevam <fabio.estevam@freescale.com> Cc: Tim Harvey <tharvey@gateworks.com> Cc: Stefano Babic <sbabic@denx.de> Cc: Tom Rini <trini@ti.com> Cc: Marek Vasut <marex@denx.de> Reviewed-by: NMarek Vasut <marex@denx.de> Signed-off-by: NNikita Kiryanov <nikita@compulab.co.il> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
由 Nikita Kiryanov 提交于
Add support for M25PE16 and M25PX16 Cc: Marek Vasut <marex@denx.de> Acked-by: NMarek Vasut <marex@denx.de> Signed-off-by: NNikita Kiryanov <nikita@compulab.co.il> Reviewed-by: NJagannadha Sutradharudu Teki <jaganna@xilinx.com>
-
-
由 Robert Baldyga 提交于
Since dev->req_seq value is initialized from "reg" property of fdt node, there is posibility, that address value contained in fdt is greater than INT_MAX, and then value in dev->req_seq is negative which led to probe() fail. This patch fix this problem by ensuring that req_seq is positive, unless it's one of errno codes. Signed-off-by: NRobert Baldyga <r.baldyga@samsung.com> Acked-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
Allow serial_find_console_or_panic() to work without a device tree. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
The sequence number support in driver model requires device tree control. It should be skipped if CONFIG_OF_CONTROL is not defined, and should not require functions from fdtdec. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
The list is supposed to be terminated with a NULL name, but is not. If a board probes a chip which does not appear in the table, U-Boot will crash (at least on sandbox). Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
A merge error ended up repeating a similar sentence twice. Fix it. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 23 9月, 2014 1 次提交
-
-
- 22 9月, 2014 3 次提交
-
-
由 Simon Glass 提交于
The get_maintainers script is a useful default, but sometimes is copies too many people, or takes a long time to run. Add an option to disable it and update the README. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
由 Simon Glass 提交于
This check should now be done whatever mode buildman is running in, since we may be displaying information while building. Signed-off-by: NSimon Glass <sjg@chromium.org>
-
- 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>
-
- 21 9月, 2014 1 次提交
-
-
由 Albert ARIBAUD 提交于
-