- Sep 05, 2014
-
-
Simon Glass authored
It seems that this is no longer needed, since checkpatch.pl will catch whitespace problems in patches. Also the option is not widely used, so it seems safe to just remove it. Suggested-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
It seems that doctest behaves differently now, and some of the unit tests do not run. Adjust the tests to work correctly. ./tools/patman/patman --test <unittest.result.TestResult run=10 errors=0 failures=0> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This code came from a different project with 2-character indentation. Fix it for U-Boot. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Sep 02, 2014
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@ti.com>
-
git://git.denx.de/u-boot-usbTom Rini authored
-
git://git.denx.de/u-boot-arcTom Rini authored
-
Bo Shen authored
When enable debug option to compile, it will give the following warning, this patch is used to get rid of it. --->8--- warning: 'flags' is used uninitialized in this function [-Wuninitialized] ---8<--- Signed-off-by:
Bo Shen <voice.shen@atmel.com>
-
Bo Shen authored
When enable debug option to compile, it will give the following warning, this patch is used to get rid of it. --->8--- warning: 'flags' is used uninitialized in this function [-Wuninitialized] ---8<--- Signed-off-by:
Bo Shen <voice.shen@atmel.com>
-
Stephen Warren authored
This allows the USB code to determine whether a USB bus reset was issued, which in turn allows the code to differentiate between a detach (return to shell prompt) and a board reset/reboot request. Signed-off-by:
Stephen Warren <swarren@nvidia.com>
-
Łukasz Majewski authored
New dfu_usb_get_reset() method is necessary to distinct two different use cases of dfu-util program. This method checks if the USB bus reset has been really performed after DFU DETACH. Without this function the previous DFU behavior is preserved. Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com>
-
Łukasz Majewski authored
This commit provides distinction between DFU device detach and reset. The -R behavior is preserved with proper handling of the dfu-util's -e switch, which detach the DFU device. By running dfu-util -e; one can force device to finish the execution of dfu command on target and execute some other scripted commands. Moreover, some naming has been changed - the dfu_reset() method now is known as dfu_detach(). New name better reflects the purpose of the code. It was also necessary to increase the number of usb_gadget_handle_interrupts() calls since we also must wait for detection of the USB reset event. Example usage: 1. -e (detach) switch dfu-util -a0 -D file1.bin;dfu-util -a3 -D uImage;dfu-util -e access to u-boot prompt. 2. -R (reset) switch dfu-util -a0 -D file1.bin;dfu-util -R -a3 -D uImage target board reset Signed-off-by:
Lukasz Majewski <l.majewski@samsung.com> Reviewed-by:
Stephen Warren <swarren@nvidia.com> Tested-by:
Stephen Warren <swarren@nvidia.com>
-
git://git.denx.de/u-boot-dmTom Rini authored
-
Vasili Galka authored
Some drivers (e.g. net/e1000) reference these functions. So, this fixes the build of MVBC_P board. I'm not familiar with the MPC5xxx platform, maybe a full implementation shall be implemented instead of this stub in the future. Signed-off-by:
Vasili Galka <vvv444@gmail.com> Cc: Wolfgang Denk <wd@denx.de>, Marek Vasut <marex@denx.de> Acked-by:
Wolfgang Denk <wd@denx.de>
-
- Sep 01, 2014
-
-
Simon Glass authored
Add a bank of GPIOs for sandbox which can be used for testing this functionality. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
The gpio command mostly relies on gpio_request() and gpio_free() being nops, in that you can request a GPIO twice. With driver model this is now implemented correctly, so it fails. Change the command to deal with a failure to claim the GPIO. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
The GPIO list is very long in many cases and most of them are not used. By default, show only the GPIOs that are in use, and provide a flag to show all of them. This makes the 'gpio status' command much more pleasant. In order to do this, driver model now exposes a method for obtaining the 'function' of a GPIO, which describes whether it is an input or output, for example. Implementation of this method is optional. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Aug 31, 2014
-
-
Masahiro Yamada authored
The QS Systems TQMa6 board support was added by commit cb07d74e and lost by commit e82abaeb. Commit e82abaeb merged the IMX branch based on pre-Kconfig and the mainline based on post-Kconfig, simply deleting the boards.cfg file. As a result, some boards added just before the merge were lost. This commit adds Kconfig, defconfig, MAINTAINERS for TQMa6 board to work on the Kconfig infrastructure. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Markus Niebel <Markus.Niebel@tq-group.com> Cc: Stefano Babic <sbabic@denx.de>
-
git://git.denx.de/u-boot-niosTom Rini authored
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Nomadik board select menu to nomadik/Kconfig. Move also common settings (CONFIG_SYS_CPU="arm926ejs" and CONFIG_SYS_SOC="nomadik"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Masahiro Yamada authored
Move Highbank-specific settings to highbank/Kconfig. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Rob Herring <robh@kernel.org>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Orion5x board select menu to orion5x/Kconfig. Move also common settings (CONFIG_SYS_CPU="arm926ejs" and CONFIG_SYS_SOC="orion5x"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Keystone board select menu to keystone/Kconfig. Move also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="keystone"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by:
Tom Rini <trini@ti.com> Cc: Vitaly Andrianov <vitalya@ti.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the OMAP5 board select menu to omap5/Kconfig. Move also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="omap5"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by:
Tom Rini <trini@ti.com> Cc: Lokesh Vutla <lokeshvutla@ti.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the OMAP4 board select menu to omap4/Kconfig. Move also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="omap4"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by:
Tom Rini <trini@ti.com> Cc: Lokesh Vutla <lokeshvutla@ti.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the OMAP3 board select menu to omap3/Kconfig. Move also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="omap3 Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by:
Tom Rini <trini@ti.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Davinci board select menu to davinci/Kconfig. Move also common settings (CONFIG_SYS_CPU="arm926ejs" and CONFIG_SYS_SOC="davinci"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by:
Tom Rini <trini@ti.com> Cc: Heiko Schocher <hs@denx.de> Cc: Sandeep Paulraj <s-paulraj@ti.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Exynos board select menu to exynos/Kconfig. Consolidate also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="exynos"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by:
Minkyu Kang <mk7.kang@samsung.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the KirkWood board select menu to kirkwood/Kconfig. Consolidate also common settings (CONFIG_SYS_CPU="arm926ejs" and CONFIG_SYS_SOC="kirkwood"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by:
Prafulla Wadasdkar <prafulla@marvell.com> Cc: Luka Perkov <luka@openwrt.org>
-
Masahiro Yamada authored
Move Versatile-specific settings to versatile/Kconfig. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Rmobile board select menu to rmobile/Kconfig. Consolidate also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="rmobile"). Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Cc: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Tegra board select menu to tegra/Kconfig. Insert the Tegra SoC select menu between the arch select and the board select. Architecture select |-- Tegra Platform (Tegra) |- Tegra SoC select (Tegra20 / 30 / 114 / 124) |- Board select Consolidate also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="tegra*") and always "select" CONFIG_SPL as follows: config TEGRA bool select SPL Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by:
Stephen Warren <swarren@nvidia.com> Cc: Tom Warren <twarren@nvidia.com>
-
Masahiro Yamada authored
Becuase the board select menu in arch/arm/Kconfig is too big, move the Zynq board select menu to zynq/Kconfig. Consolidate also common settings (CONFIG_SYS_CPU="armv7" and CONFIG_SYS_SOC="zynq"). Refactor board/xilinx/zynq/MAINTAINERS too. Signed-off-by:
Masahiro Yamada <yamada.m@jp.panasonic.com> Tested-by:
Michal Simek <michal.simek@xilinx.com>
-
- Aug 30, 2014
-
-
Benoît Thébaudeau authored
Commit 41623c91 'arm: move exception handling out of start.S files' missed some linker scripts. Hence, some boards no longer had exception handling linked since this commit. Restore the original behavior by adding the .vectors section to these linker scripts. Signed-off-by:
Benoît Thébaudeau <benoit.thebaudeau.dev@gmail.com> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
-
Holger Brunck authored
Newer FLASH types used on these boards don't allow writing of subpages. So disable subpage write in the NAND driver. Additionally we need to tell the UBI layer in the kernel that he also should only write 2048 bytes. This is done with an additional command line parameter for the kernel commandline. Signed-off-by:
Holger Brunck <holger.brunck@keymile.com> cc: Valentin Longchamp <valentin.longchamp@keymile.com> cc: Prafulla Wadaskar <prafulla@marvell.com>
-
Holger Brunck authored
Make it configurable to disable subpage writes like the DaVinci NAND driver already does. Signed-off-by:
Holger Brunck <holger.brunck@keymile.com> cc: Valentin Longchamp <valentin.longchamp@keymile.com> cc: Prafulla Wadaskar <prafulla@marvell.com> cc: Scott Wood <scottwood@freescale.com>
-
Tom Rini authored
Add support for booting Images and for unzipping Image.gz files. Signed-off-by:
Tom Rini <trini@ti.com>
-
Tom Rini authored
- Drop DEBUG - Drop defines we can use the default of. - Provide a larger malloc pool. - Correct default locations for kernel / initrd / device tree Signed-off-by:
Tom Rini <trini@ti.com>
-
Tom Rini authored
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:
Tom Rini <trini@ti.com>
-
Tom Rini authored
The Documentation/arm64/booting.txt document says that pass in x1/x2/x3 as 0 as they are reserved for future use. Signed-off-by:
Tom Rini <trini@ti.com>
-
Steve Rae authored
Convert the bcm958300k and the bcm958622hr boards from "boards.cfg" to Kconfig. Signed-off-by:
Steve Rae <srae@broadcom.com>
-