Signed-off-by: NChristian Gmeiner <christian.gmeiner@gmail.com>

Fix warning due to missing prototype for writel
Signed-off-by: NStefano Babic <sbabic@denx.de>
Acked-by: NStefan Roese <sr@denx.de>

To align with other mx6 boards, change ENV offset from 384KB to
512KB position to fit a larger u-boot image.
Signed-off-by: NYe.Li <B37916@freescale.com>

Add board level spl support for mx6sxsabresd board.
Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>

Since mx6sx's memory space is different to mx6dq, redefine the SPL
related macro for mx6sx chip.
Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>

Define two structure mx6sx_iomux_ddr_regs and mx6sx_iomux_grp_regs.
Add a new function mx6sx_dram_iocfg to configure dram io.

Since mx6sx only have one channel mmdc0, define a new empty macro MMDC1
to replace mmdc1->entry=value for mx6sx. And to other mx6 soc, MMDC1
effects as "mmdc1->entry=value".
Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>

Add SPL support in mx6sxsabresd header file.
Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>

select SUPPORT_SPL for mx6sxsabresd.
Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>

Add a SPL default configuration file for mx6sxsabresd board.
Signed-off-by: NPeng Fan <Peng.Fan@freescale.com>

Add support for the NAND Flash chip with page size of 4096+224-bytes OOB area length

For example Micron MT29F4G08 NAND flash device defines a OOB area which is
224 bytes long (oobsize).
Signed-off-by: NAlexandre Coffignal <acoffignal@geral.com>

This patch adds the new Barco platinum platform. It currently
includes those two boards:

platinum-titanium
-----------------
This is the same board as the titanium that is already supported in
mainline U-Boot. But its now moved to this new platform to support
multiple "flavors" of imx6 boards in one directory. Its also moved
to support SPL booting. And with this we use the run-time DDR
configuration of this SPL support. The board is equipped with the
Micron MT41J128M16JT-125 DDR chips. We now can remove the DDR
related registers tuples from the imximage.cfg file. As all this
is done in the SPL at run-time.

platinum-picon
--------------
This board is new and based on the MX6DL with 1GiB DDR using the
Micron MT41K256M16HA DDR3 chips. Its also equipped with 2 NAND
chips (each 512MiB).
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Stefano Babic <sbabic@denx.de>
Cc: Pieter Ronsijn <pieter.ronsijn@barco.com>

Since commit 1f98e31b ("imx: mx6sxsabresd: Use the pfuze common init
function") board_late_init() became empty, so we can safely remove this unneeded
function.
Signed-off-by: NFabio Estevam <fabio.estevam@freescale.com>

The Fusion LCD needs the 32bit color depth to properly work; the
default is different on the 3.10.17 kernels and it is better to ensure
it work out of box using proper default color setting.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

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>