Now that "usb start" will only start usb if not already started, we can simply
call "usb start" whenever we (may) need access to usb devices, and it will only
actually scan the bus at the first call.
Signed-off-by: NHans de Goede <hdegoede@redhat.com>

Currently we've this magic in include/config_distro_bootcmd.h to avoid
scanning the usb bus multiple times.

And it does not work when also using an usb keyboard because then the
preboot command has already scanned the bus, so we're still scanning it
twice.

This commit makes "usb start" only start usb if it is no already started,
allowing us to remove all the magic for it from include/config_distro_bootcmd.h
and just call it unconditionally.

This also causes "usb start" and "usb reset" to actually do what their
different names suggest, rather then both of them doing exactly the same.
Signed-off-by: NHans de Goede <hdegoede@redhat.com>

Fix use-before-initialized bug in pxa25x_udc driver.

Function usb_gadget_register_driver calls udc_disable,
and udc_disable calls pullup_off that uses dev->mach->udc_command.
But dev->mach is initialized in usb_gadget_register_driver after
calling udc_disable. This patch fixes the order of initialization.
Signed-off-by: NAlex Sadovsky <Nable.MainInbox@googlemail.com>

Without this function the USB compliance test (USB 2.0 Command Verifier) will
fail in the "Interface Descriptor Test" with this error message:

FAIL
(1.2.51) A successful GetInterface request must return the alternate setting
set by a prior call to SetInterface.

Lets add this function to read back the value so that the DFU device fully
passes the USB compliance test.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Roger Meier <r.meier@siemens.com>
Cc: Samuel Egli <samuel.egli@siemens.com>
Cc: Enrico Leto <enrico.leto@siemens.com>
Acked-by: NHeiko Schocher <hs@denx.de>
Cc: Lukasz Majewski <l.majewski@samsung.com>
Cc: Marek Vasut <marex@denx.de>

On the DXR2 board (AM335x using MUSB) the USB compliance test suite
(USB 2.0 Command Verifier) will cause the board to crash and reset
upon the "BOS Descriptor Test - Addressed state". Here the output
from the DRX2 while running this test:

GADGET DRIVER: usb_dnl_dfu
musb-hdrc: peripheral reset irq lost!
composite_setup (776)
data abort
pc : [<87f693ac>]          lr : [<87f6911c>]
sp : 86f33a58  ip : 00000000     fp : 86f3bbac
r10: 00000f00  r9 : 86f33ef4     r8 : 86f37da8
r7 : 00000005  r6 : 86f33a90     r5 : 00000000  r4 : 86f37e30
r3 : 00000000  r2 : 00000000     r1 : 87f9c888  r0 : 00000016
Flags: Nzcv  IRQs off  FIQs on  Mode SVC_32
Resetting CPU ...

resetting ...

By adding the case statement for USB_DT_BOS and therefore not running
into the default case (jump to unkown label) this crash is fixed.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Roger Meier <r.meier@siemens.com>
Cc: Samuel Egli <samuel.egli@siemens.com>
Cc: Enrico Leto <enrico.leto@siemens.com>
Acked-by: NHeiko Schocher <hs@denx.de>
Cc: Lukasz Majewski <l.majewski@samsung.com>
Cc: Marek Vasut <marex@denx.de>

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>

Allow booting the OpenRTOS payloads via fitImage image type.
Signed-off-by: NMarek Vasut <marex@denx.de>
Cc: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Add separate image type for the Wittenstein OpenRTOS .
Signed-off-by: NMarek Vasut <marex@denx.de>
Cc: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Add support for Seagate BlackArmor NAS220
Signed-off-by: NEvgeni Dobrev <evgeni@studio-punkt.com>

Some MTD defines are repeated twice; once with UBI and then with MTD.
Remove the duplicate MTD defines from the UBI grouping.
Signed-off-by: NBill Pringlemeir <bpringlemeir@nbsps.com>

This allows the caller to easily detect how much of the destination buffer
has been used.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This allows the caller to easily detect how much of the destination buffer
has been used.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This allows the caller to easily detect how much of the destination buffer
has been used.
Signed-off-by: NSimon Glass <sjg@chromium.org>