07 May, 2018

1 commit

  • When U-Boot started using SPDX tags we were among the early adopters and
    there weren't a lot of other examples to borrow from. So we picked the
    area of the file that usually had a full license text and replaced it
    with an appropriate SPDX-License-Identifier: entry. Since then, the
    Linux Kernel has adopted SPDX tags and they place it as the very first
    line in a file (except where shebangs are used, then it's second line)
    and with slightly different comment styles than us.

    In part due to community overlap, in part due to better tag visibility
    and in part for other minor reasons, switch over to that style.

    This commit changes all instances where we have a single declared
    license in the tag as both the before and after are identical in tag
    contents. There's also a few places where I found we did not have a tag
    and have introduced one.

    Signed-off-by: Tom Rini

    Tom Rini
     

19 Jun, 2014

1 commit

  • commit 18b06652cd "tools: include u-boot version of sha256.h"
    unconditionally forced the sha256.h from u-boot to be used
    for tools instead of the host version. This is fragile though
    as it will also include the host version. Therefore move it
    to include/u-boot to join u-boot/md5.h etc which were renamed
    for the same reason.

    cc: Simon Glass
    Signed-off-by: Jeroen Hofstee

    Jeroen Hofstee
     

15 Oct, 2013

1 commit


24 Jul, 2013

1 commit


22 Jan, 2010

1 commit


20 Jul, 2009

1 commit

  • Shove a lot of the HOSTCC and related #ifdef checking crap into the new
    compiler.h header so that we can keep all other headers nice and clean.

    Also introduce custom uswap functions so we don't have to rely on the non
    standard implementations that a host may (or may not in the case of OS X)
    provide. This allows mkimage to finally build cleanly on an OS X system.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

04 Apr, 2009

1 commit

  • Add support for compiling the host tools in the tools directory using
    the MinGW toolchain. This produces executables which can be used on
    standard Windows computers without requiring cygwin.

    One must specify the MinGW compiler and strip utilities as if they
    were the host toolchain in order to build win32 executables, eg:

    make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools

    Signed-off-by: Peter Tyser

    Peter Tyser
     

10 Jul, 2007

1 commit


23 Jun, 2007

1 commit

  • - Show on the Status LEDs, some States of the board.
    - Get the MAC addresses from the EEProm
    - use PREBOOT
    - use the CF on the board.
    - check the U-Boot image in the Flash with a SHA1
    checksum.
    - use dynamic TLB entries generation for the SDRAM

    Signed-off-by: Heiko Schocher

    Heiko Schocher