It is often necessary to "break in" into boards bootloader commandline if
something fails or even for development purposes some parameters have to be
changed.

So we enable u-boot's CONFIG_NETCONSOLE feature.
We also modify Networksettings to apply with this new use-case.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

On boards were we have no NAND-flash soldered, we want to use those free pins
as regular gpio.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

since we have a dtb blob programmed on the board we try to setup the cpsw
interface with the programmed mac.
If this method fails, we fall back to the device-fuses.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

a summary screen to the lcd.
Values are taken from environment and or devicetree blob.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Sometimes we do not want redirect u-boot's console to screen but anyway we want
write out some status information out of a u-boot script to the display.

So we cannot use the normal "echo ....", instead we write explicitly using
"lcdputs ..." for writing to the actual cursor position on LCD.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Sometimes we do not want redirect u-boot's console to screen but anyway we want
write out some status information out of a u-boot script to the display.

To define the specific position of the string to be written, we have to set
the cursor with "setcurs" before writing.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Often on boards exists a circuit which switches power on/off to LCD display.
Due to the need of limiting the in-rush current the output voltage from this
circuit rises "slowly", so it is necessary to wait a bit (VCC ramp up time)
before starting output on LCD-pins.
This time is specified in <n> ms within the panel-settings, called "pup_delay"

Further some LCDs need a couple of frames to stabilize the image on it.
We have now the possibility to wait some time after starting output on LCD.
This time is also specified in <n> ms within panel-settings, called "pon_delay"
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

Without this change the board support for these SPEAr boards would
be dropped soon. Generic board support seems to work just fine.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Vipin Kumar <vk.vipin@gmail.com>
Acked-by: NViresh Kumar <viresh.kumar@linaro.org>

- DMA threshold mode can be selected in board config head file.
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>

Board can define its own AXI burst length to improve DWMAC DMA performance.

v2-changes:
- Avoid write burst len register when the Macro is not defined.

v3-changes:
- Add axi_bus register member to struct eth_dma_regs.
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>
Acked-by: NJoe Hershberger <joe.hershberger@ni.com>

Bring checkstack.pl up to date from its upstream Linux development.
Effectively, the following linux commits:

208ad00 checkstack.pl: port to AArch64
fda9f99 scripts/checkstack.pl: automatically handle 32-bit and 64-bit mode for ARCH=x86
7eb6e34 kbuild: trivial - remove trailing empty lines
690998b scripts/checkstack.pl: Add metag support
Reported-by: NYork Sun <yorksun@freescale.com>
Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
Signed-off-by: NKim Phillips <kim.phillips@freescale.com>

Currently, an environment variable must be used to store the randomly
generated UUID for each partition. This is not necessary, so make storing
the UUID optional. Now passing uuid_disk and uuid are optional when random
UUIDs are enabled.
Signed-off-by: NRob Herring <robh@kernel.org>
Acked-by: NPrzemyslaw Marczak <p.marczak@samsung.com>

The gpt command always reports success even if writing the partition table
failed. Propagate the return value of gpt_restore so we get proper status
reported.
Signed-off-by: NRob Herring <robh@kernel.org>
Reviewed-by: NPrzemyslaw Marczak <p.marczak@samsung.com>

enable generic board support for the ipam390 board.
Signed-off-by: NHeiko Schocher <hs@denx.de>

- adapt to build with eldk-5.4
- add more targets for building with buildman:
  - freescale -x arm,m68k,aarch64
  - arm1136
  - arm1176
  - arm720t
  - arm920t
  - davinci
  - kirkwood
Signed-off-by: NHeiko Schocher <hs@denx.de>
Reviewed-by: NRoger Meier <r.meier@siemens.com>

According to table 2-3 on page 87 of Marvell's latest PXA270
Specification Update Rev. I from 2010.04.19 [1] there exists a breed of
chips with a new CPU ID for PXA270M A1 stepping which our latest
Colibri PXA270 V2.4A modules actually have assembled. This patch helps
in correctly identifying those chips upon boot as well which then looks
as follows:

CPU: Marvell PXA27xM rev. A1

[1] http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_spec_update.pdfAcked-by: NMarek Vasut <marex@denx.de>

Fix the name appearing in menuconfig for memtest command
Signed-off-by: NNikolaos Pasaloukos <Nikolaos.Pasaloukos@imgtec.com>
Cc: Masahiro Yamada <yamada.m@jp.panasonic.com

Boards need to select CONFIG_SYS_GENERIC_BOARD in order to
prevent removal from the project.
Signed-off-by: NStefano Babic <sbabic@denx.de>

Boards need to select CONFIG_SYS_GENERIC_BOARD in order to
prevent removal from the project.
Signed-off-by: NStefano Babic <sbabic@denx.de>

Boards need to select CONFIG_SYS_GENERIC_BOARD in order to
prevent removal from the project.
Signed-off-by: NStefano Babic <sbabic@denx.de>

In 0200020b we added a number of tests for 'if
defined(CONFIG_SYS_FSL_SEC_LE) && !defined(CONFIG_MX6)' and
accidentally did one as 'ifdef defined...'
Signed-off-by: NTom Rini <trini@konsulko.com>

commit d9f43c8f sets
get_reset_cause() as static, but this conflicts with mx5
where its prototype is in sys_proto.h.

Drop it from sys_proto.h and drop print_cpuinfo from mx53_loco,
factorizing the call for this board.
Signed-off-by: NStefano Babic <sbabic@denx.de>
CC: Jason Liu <jason.hui@linaro.org>

Currently in some cases SDRAM init requires global_data to be available
and soon this will not be available prior to board_init_f().  Adjust the
code paths in these cases to be correct.  In some cases we had the SPL
stack be in DDR as we might have large stacks (due to Falcon Mode +
Environment).  In these cases switch to CONFIG_SPL_STACK_R.  In other
cases we had simply been setting CONFIG_SPL_STACK into SRAM.  In these
cases we no longer need to (CONFIG_SYS_INIT_SP_ADDR is used and is also
in SRAM) so drop those lines.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Tested on Beagleboard, Beagleboard xM
Tested-by: NMatt Porter <mporter@konsulko.com>
Tested on Beaglebone Black, AM43xx GP EVM, OMAP5 uEVM, OMAP4 Pandaboard
Tested-by: NTom Rini <trini@konsulko.com>
Signed-off-by: NTom Rini <trini@konsulko.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

When CONFIG_SYS_MALLOC_SIMPLE is defined, free() is a static inline. Make
sure that the export interface still builds in this case.
Signed-off-by: NSimon Glass <sjg@chromium.org>

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>

Use the full driver model GPIO and serial drivers in SPL now that these are
supported. Since device tree is not available they will use platform data.

Remove the special SPL GPIO function as it is no longer needed.

This is all in one commit to maintain bisectability.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is already set up in crt0.S. We don't need a new structure and don't
really want one in the 'data' section of the image, since it will be empty
and crt0.S's changes will be ignored.

As an interim measure, remove it only if CONFIG_DM is not defined. This
allows us to press ahead with driver model in SPL and allow the stragglers
to catch up.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This function has grown into something of a monster. Some boards are setting
up a console and DRAM here in SPL. This requires global_data which should be
set up in one place (crt0.S).

There is no need for SPL to use s_init() for anything since board_init_f()
is called immediately afterwards.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This commit removes the dram reservation from board file,
because it is done in a common code.
Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com>
Cc: Minkyu Kang <mk7.kang@samsung.com>
Signed-off-by: NMinkyu Kang <mk7.kang@samsung.com>

This commit enables the last DRAM bank and reserves
the last 22 MiB of it, for the secure firmware.
Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com>
Cc: Akshay Saraswat <akshay.s@samsung.com>
Cc: Hyungwon Hwang <human.hwang@samsung.com>
Cc: Minkyu Kang <mk7.kang@samsung.com>
Signed-off-by: NMinkyu Kang <mk7.kang@samsung.com>

Since more than one board requires memory reservation
for the secure firmware, the reservation code can be
made in a common code.
Now, to reserve some part of the the last bank,
board config should define:
- CONFIG_TZSW_RESERVED_DRAM - len in bytes
- CONFIG_NR_DRAM_BANKS - number of memory banks
Signed-off-by: NPrzemyslaw Marczak <p.marczak@samsung.com>
Cc: Akshay Saraswat <akshay.s@samsung.com>
Cc: Hyungwon Hwang <human.hwang@samsung.com>
Cc: Minkyu Kang <mk7.kang@samsung.com>
Signed-off-by: NMinkyu Kang <mk7.kang@samsung.com>

This patch suppress following warning:

board/samsung/common/board.c:95:32: warning: iteration 4u invokes undefined behavior [-Waggressive-loop-optimizations]
   addr = CONFIG_SYS_SDRAM_BASE + (i * SDRAM_BANK_SIZE);
                                ^
board/samsung/common/board.c:94:2: note: containing loop

about possible signed integer overflow at gcc 4.8.2 (odroid board)
Signed-off-by: NLukasz Majewski <l.majewski@samsung.com>
Signed-off-by: NMinkyu Kang <mk7.kang@samsung.com>

Signed-off-by: NTom Rini <trini@konsulko.com>