- Feb 12, 2015
-
-
Simon Glass authored
Move this option to Kconfig and update all boards. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
With driver model the number of PIO ports is defined by platform data, so remove it from the header file. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Andreas Bießmann <andreas.devel@googlemail.com>
-
Nobuhiro Iwamatsu authored
This adds driver model support with this driver. This was tested by Koelsch board and Gose board. Signed-off-by:
Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Ian Campbell <ijc@hellion.org.uk>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config headers and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Remove driver model CONFIGs from the board config header and use Kconfig instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add Kconfig settings for these two options. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Simon Glass authored
Add a file to control driver model test features. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Simon Glass authored
The SPL support cannot be enabled yet, but we can add the Kconfig options in preparation for this. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Expand the help messages for each driver. Add missing Kconfig for I2C, SPI flash and thermal. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Simon Glass authored
Add a suitable Kconfig for this directory. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Masahiro Yamada <yamada.m@jp.panasonic.com>
-
Simon Glass authored
Make the driver model I2C API available always, even if driver model is not enabled. This allows for a 'soft' switch-over, where drivers can use the new structures in code which is compiled but not yet used. This makes migration easier in some cases. Fix up the existing drivers which define their own 'struct i2c_msg'. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Heiko Schocher <hs@denx.de>
-
Simon Glass authored
As with i2c_read() and i2c_write(), add a dm_ prefix to the driver model versions of these functions to avoid conflicts. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Heiko Schocher <hs@denx.de>
-
Simon Glass authored
Drop the old checksum functions in favour of the new ones. Signed-off-by:
Simon Glass <sjg@chromium.org> Acked-by:
Joe Hershberger <joe.hershberger@ni.com>
-
Stefan Roese authored
This also displays the "Board:" line in the bootup text with the generic board support code. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Simon Glass <sjg@chromium.org> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Stefan Roese authored
These additional nodes need to be provided to get U-Boot to boot correctly on the Canyonlands / Glacier board: - chosen path to the console-uart - reg-shift set to 0 in the uart device nodes Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Simon Glass <sjg@chromium.org> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Stefan Roese authored
This is necessary, as ppc4xx has the reset vector located at the end of the U-Boot image. This needs to be flashed to the end of the NOR flash. Adding the dtb to the main U-Boot image will break booting on ppc4xx. This patch now embeds the dtb in the U-Boot image instead. Signed-off-by:
Stefan Roese <sr@denx.de> Cc: Simon Glass <sjg@chromium.org> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This permits us to use linux/linkage.h on PowerPC machines. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Adjust Kconfig to default to driver model for glacier, canyonlands and arches. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This uses the ns16550 driver but sets up the clock at run-time. It does not seem to be available in the device tree. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This comes from the device tree or a call to get_uart_clock(). Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Enable CONFIG_OF_CONTROL so that U-Boot on these three boards uses a device tree for its configuration. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Define an _end symbol indicating the end of u-boot.bin. Also add some dummy words into the link script to ensure that u-boot.bin will always extend that far. There may be a better way of doing this. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
This is required at present for device tree control. The ppc4xx does support GPIOs but does not seem to have a proper driver. So this file is empty. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Call this function to set up our early memory. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
The canyonlands.h config file works with canyonlands, glacier and arches boards. Bring in the device tree files for these from Linux 3.17. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Switch to generic board so that this board will not be broken/removed. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Add a new ramboot config for glacier so that it is possible to test U-Boot loaded over Ethernet instead of using JTAG. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Move these options to Kconfig and remove them from the CONFIG files. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Many CONFIG options have an unnecessary value of 1. CONFIG_440 is set in the various board config files. Also simplify the CONFIG_440 check in config.mk Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
Enable this in the Kconfig so that PowerPC boards can use device tree to configure U-Boot. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Simon Glass authored
At present on some architectures we set up the following before calling board_init_f(): - global_data - stack - early malloc memory Adding the code to support early malloc and global data setup to every arch's assembler start-up is a pain. Also this code is not actually architecture-specific. We can use common code for all architectures and with a bit of care we can write this code in C. Add a new function to deal with this. It should be called after memory is available, with a pointer to the top of the area that should be used before relocation. The function will set things up and return the lowest memory address that it allocated/used. That can then be set as the top of the stack. Note that on some archs this function will use the stack, so the stack pointer should be set to same value as is pased to board_init_f_mem(). A margin of 128 bytes will be left for this stack, so that it is not overwritten. This means that 64 bytes is wasted by this early call. This is not strictly necessary on several more modern archs, so we could remove this at the cost of some arch-dependent code. With this function there is no-longer any need for the assembler code to zero global_data or set up the early malloc pointers. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
Hans de Goede authored
All callers of malloc should already do error checking, and may even be able to continue without the alloc succeeding. Moreover, common/malloc_simple.c is the only user of .rodata.str1.1 in common/built-in.o when building the SPL, triggering this gcc bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54303 Causing .rodata to grow with e.g. 0xc21 bytes, nullifying all benefits of using malloc_simple in the first place. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Acked-by:
Simon Glass <sjg@chromium.org>
-