T1024RDB-PB board adds 2.5G SGMII support with AQR105 PHY.
rcw_0x095 is used for 10G XFI + 3x PCIex1
rcw_0x135 is used for 2.5G SGMII + 2x PCIex1
Signed-off-by: NShengzhou Liu <Shengzhou.Liu@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

A new deep sleep interface is introduced to support generic
board structure. Converts it to use new interface.

Besides, added SPI/SD/NAND boot deep sleep support.
Signed-off-by: NTang Yuantian <Yuantian.Tang@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

Add missing T1024QDS_defconfig for NOR boot on T1024QDS.
Signed-off-by: NShengzhou Liu <Shengzhou.Liu@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

Add serdes protocol 0x40 and 0x5f.
Signed-off-by: NShengzhou Liu <Shengzhou.Liu@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

Secure boot target is added for T1042RDB platform.
Signed-off-by: NGaurav Rana <gaurav.rana@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

CONFIG_BOOTDELAY is missing from board header file. Add this macro
to enable counting down of auto boot.
Signed-off-by: NHarninder Rai <harninder.rai@freescale.com>
[York Sun: Add commit message]
Reviewed-by: NYork Sun <yorksun@freescale.com>

CONFIG_SYS_PBI_FLASH_BASE is defined for Secure Boot on C29X
Signed-off-by: NAneesh Bansal <aneesh.bansal@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

For B4 the LIODN register for PCIe is in PCIe address space and not in
GUTs
Signed-off-by: NPoonam Aggrwal <poonam.aggrwal@freescale.com>
Signed-off-by: NVarun Sethi <Varun.Sethi@freescale.com>
Signed-off-by: NShaveta Leekha <shaveta@freescale.com>
Signed-off-by: NLaurentiu Tudor <Laurentiu.Tudor@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

SerDes 2 protocol 56 is not valid any longer due to
the new RCW; protocol 55 is used instead, so add
SerDes 2 protocol 55 to align with RCW.
Signed-off-by: NChunhe Lan <Chunhe.Lan@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

If CONFIG_OF_CONTROL is enabled, lib/fdtdec.c is compiled.
It includes <asm/gpio.h> and then <asm/gpio.h> includes
<asm/arch/gpio.h>.  As a result, all the SoCs that enable
CONFIG_OF_CONTROL must have <asm/arch/gpio.h>.

The right fix would be to split the lib/fdtdec.c to remove
dependency on GPIO.

This commit adds a dummy <asm/arch/gpio.h> to support OF_CONTROL
for mpc85xx platform. A file mpc85xx_gpio.h exists in
arch/powerpc/include/asm. The defintions in that file conflict
with the ones in asm-generic/gpio.h. Hence a dummy header file
has been added. This will be removed after FDT-GPIO stuff is
fixed correctly.
Signed-off-by: NRuchika Gupta <ruchika.gupta@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

Secure boot target is added for P5040DS platform.
Signed-off-by: NGaurav Rana <gaurav.rana@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

Add NOR and SPI flash secure boot target for C29XPCIE board.
Signed-off-by: NPo Liu <Po.Liu@freescale.com>
Signed-off-by: NMingkai.Hu <Mingkai.Hu@freescale.com>
Reviewed-by: NYork Sun <yorksun@freescale.com>

All the 74xx_7xx boards are still non-generic boards:
P3G4, ZUMA, ppmc7xx, ELPPC, mpc7448hpc2
Acked-by: NMarek Vasut <marex@denx.de>
Acked-by: NStefan Roese <sr@denx.de>
Acked-by: NYork Sun <yorksun@freescale.com>
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
Cc: Wolfgang Denk <wd@denx.de>
Cc: Nye Liu <nyet@zumanetworks.com>
Cc: Roy Zang <tie-fei.zang@freescale.com>

Now TQM8xx is the only remaining board family of mpc8xx.
It uses its own linker script, board/tqc/tqm8xx/u-boot.lds.

arch/powerpc/cpu/mpc8xx/u-boot.lds is not used by any boards.
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
Cc: Wolfgang Denk <wd@denx.de>

Since commit 843125da (ppc4xx: remove HH405 board), CONFIG_HH405
is not defined.

Since commit d5263304 (ppc4xx: remove PMC405), CONFIG_PMC405
is not defined.
Acked-by: NStefan Roese <sr@denx.de>
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
Cc: Matthias Fuchs <matthias.fuchs@esd.eu>

Normally buildman runs with 'make -s' meaning that only errors and warnings
appear in the log file. Add a -V option to run make in verbose mode, and
with V=1, causing a full build log to be created.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The site at https://www.kernel.org/pub/tools/crosstool/ is a convenient
repository of toolchains which can be used for U-Boot. Add a feature to
download and install a toolchain for a selected architecture automatically.

It isn't clear how long this site will stay in the current place and
format, but we should be able to rely on bug reports if it changes.
Suggested-by: NMarek Vašut <marex@denx.de>
Suggested-by: NFabio Estevam <festevam@gmail.com>
Signed-off-by: NSimon Glass <sjg@chromium.org>

Some archs have need than one alias, so support a list of alises in the
..buildman file.
Signed-off-by: NSimon Glass <sjg@chromium.org>

We should create a test setting file when running testes, not use whatever
happens to be on the local machine.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Silently ignore this since it is valid to have missing sections.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This file is only partially documented. Add some more details.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Suggested-by: NWolfgang Denk <wd@denx.de>

Since we need a few modules which might not be available in a bare-bones
distribution, add a note about that to the README.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Suggested-by: NWolfgang Denk <wd@denx.de>

In some cases there may be multiple toolchains with the same name in the
path. Provide an option to use the full path in the CROSS_COMPILE
environment variable.

Note: Wolfgang mentioned that this is dangerous since in some cases there
may be other tools on the path that are needed. So this is set up as an
option, not the default. I will need test confirmation (i.e. that this
commit fixes a real problem) before merging it.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Suggested-by: NSteve Rae <srae@broadcom.com>

If:

1. Toolchains A and B have the same filename
2. Toolchain A is in the PATH
3. Toolchain B is given in ~/.buildman and buildman uses it to build

then buildman will add toolchain B to the end of its path but will not
necessarily use it since U-Boot will find toolchain A first in the PATH.

Try to fix this by putting the toolchain first in the path instead of
last.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The assumption that the compiler name will always end in gcc is incorrect
for clang and apparently on BSD.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Adjust the -b flag to permit a range expression as well as a branch.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Suggested-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
Tested-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>

When running tests the output directory is often wiped. This is only safe if
a branch is being built. The output directory may contain other things
besides the buildman test output.
Signed-off-by: NSimon Glass <sjg@chromium.org>

When building current source for a single board, buildman puts the output
in <output_dir>/current/current/<board>. Add an option to make it use
<output_dir>/<board> instead. This removes the unnecessary directories
in that case, controlled by the --no-subdirs/-N option.
Suggested-by: NTom Rini <trini@ti.com>
Signed-off-by: NSimon Glass <sjg@chromium.org>

Buildman normally obtains the upstream commit by asking git. Provided that
the branch was created with 'git checkout -b <branch> <some_upstream>' then
this normally works.

When there is no upstream, we can try to guess one, by looking up through
the commits until we find a branch. Add a function to try this and print
a warning if buildman ends up relying on it.

Also update the documentation to match.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Suggested-by: NWolfgang Denk <wd@denx.de>

This is not needed since we always do a full (non-incremental) build. Also
it might be dangerous since it will try to delete everything below the
base directory.

Fix this potentially nasty bug.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Buildman currently puts current-source builds in a current/current
subdirectory, but there is no need for the extra depth.
Suggested-by: NAlbert Aribaud <albert.u.boot@aribaud.net>
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add a few tests of the output directory logic.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Use phys_addr_t instead of int for addresses.
Addresses can't be < 0.
Signed-off-by: NMichal Simek <michal.simek@xilinx.com>

Signed-off-by: NMichal Simek <michal.simek@xilinx.com>

Trivial fix.
Signed-off-by: NMichal Simek <michal.simek@xilinx.com>

It makes sense to specify CONFIG_SYS_CLK_FREQ in "configs/xx_defconfig"
instead of "include/configs/xxx.h" because then header will be reusable
across boards with different CPU clocks.

Also this nice to have an ability for end user to tune this value
himself via "menuconfig".

For now I'm only applying this change to all ARC configs because
otherwise scope of change will be huge.
Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com>
Cc: Tom Rini <trini@ti.com>
Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
Cc: Hans de Goede <hdegoede@redhat.com>
cc: Simon Glass <sjg@chromium.org>
Reviewed-by: NTom Rini <trini@ti.com>

If CONFIG_SPL_NOR_SUPPORT is defined, spl_nor_load_image() requires
spl_start_uboot(), CONFIG_SYS_OS_BASE, CONFIG_SYS_SPL_ARGS_ADDR,
CONFIG_SYS_FDT_BASE to be defined even if users just want to run
U-Boot, not Linux.  This is inconvenient.

This patch is following the codying style of common/spl/spl_nand.c.
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>