Eric Lee / smarc-uboot

14 Mar, 2016

1 commit

01 Mar, 2016

1 commit

16 Feb, 2016

3 commits

  • 727a25b24   Prepare v2016.03-rc2 ... Browse Code »

    Signed-off-by: Tom Rini

    Tom Rini
     
  • 7ed4848bb   Makefile: generate symbol list from u-boot ... Browse Code »

    This information may be useful for both debugging, and processes that want
    to perform simple forms of introspection on the U-Boot binary, such as
    determining the set of "ut" subtests that are compiled in.

    Signed-off-by: Stephen Warren
    Acked-by: Simon Glass

    Stephen Warren
     
  • 15b51878b   Makefile: remove BUILD_TAG from KBUILD_CFLAGS ... Browse Code »

    If BUILD_TAG is part of KBUILD_CFLAGS, then any time the value changes,
    all files get rebuilt. In a continuous integration environment, the value
    will change every build. This wastes time, assuming that incremental
    builds would otherwise occur.

    To solve this, remove BUILD_TAG from KBUILD_CFLAGS and add it to CFLAGS
    for just the one file that uses it. This does have the disadvantage that
    if any other files want to use the flag, we'll need to duplicate this
    custom CFLAGS setup logic. However, it seems unlikely we'll need this.

    An alternative would be to add BUILD_TAG to the "local version" and remove
    the special case code from display_options.c. However, that would affect
    the format of the U-Boot signon message, which may negatively affect
    people looking for specific data there. The approach of using
    file-specific CFLAGS was suggested by Masahiro Yamada.

    Signed-off-by: Stephen Warren
    Reviewed-by: Tom Rini
    Reviewed-by: Masahiro Yamada
    Acked-by: Simon Glass

    Stephen Warren
     

08 Feb, 2016

1 commit

03 Feb, 2016

1 commit

02 Feb, 2016

6 commits

  • 73c5c3999   Makefile: Drop unnecessary -dtb suffixes ... Browse Code »
    29

    When OF_CONTROL is enabled, u-boot-dtb.* files are the same as u-boot.*
    files. So we can use the latter for simplicity.

    Tested-by: Stephen Warren
    Signed-off-by: Simon Glass

    Simon Glass
     
  • dae6e7bf5   Makefile: Make u-boot.img the same as u-boot-dtb.img ... Browse Code »

    Create u-boot.img even when OF_CONTROL is enabled, so that this file can be
    used in both cases.

    Tested-by: Stephen Warren
    Signed-off-by: Simon Glass

    Simon Glass
     
  • bd7dc3883   socfpga: Simplify Makefile filenames ... Browse Code »

    We don't need the -dtb suffix anymore, so drop it.

    Tested-by: Stephen Warren
    Signed-off-by: Simon Glass

    Simon Glass
     
  • a9d78260a   tegra: Always build a boot image with the same filename ... Browse Code »

    Adjust the Makefile to build u-boot-tegra.bin which contains a device tree
    if OF_SEPARATE is enabled, and does not if not. This mirrors U-Boot's new
    approach of using u-boot.bin to handle both cases.

    Tested-by: Stephen Warren
    Signed-off-by: Simon Glass

    Simon Glass
     
  • ad1ecd206   fdt: Build a U-Boot binary without device tree ... Browse Code »
    63

    At present u-boot.bin holds the plain U-Boot binary without the device tree.
    This is somewhat annoying since you need either u-boot.bin or u-boot-dtb.bin
    depending on whether device tree is used.

    Adjust the build such that u-boot.bin includes a device tree (if enabled),
    and the plain binary is in u-boot-nodtb.bin. For now u-boot-dtb.bin remains
    the same.

    This should be acceptable since:

    - without OF_CONTROL, u-boot.bin still does not include a device tree
    - with OF_CONTROL, u-boot-dtb.bin does not change

    The main impact is build systems which are set up to use u-boot.bin as
    the output file and then add a device tree. These will have to change to use
    u-boot-nodtb.bin instead.

    Adjust tegra rules so it continues to produce the correct files.

    Tested-by: Stephen Warren
    Reviewed-by: Stephen Warren
    Signed-off-by: Simon Glass

    Simon Glass
     
  • 580cc0331   tegra: Clarify generation of -nodtb file with OF_CONTROL ... Browse Code »

    Fix the ALL-y logic in the Makefile so that is clear that we always want
    the -nodtb file.

    Tested-by: Stephen Warren
    Reviewed-by: Stephen Warren
    Signed-off-by: Simon Glass

    Simon Glass
     

25 Jan, 2016

1 commit

  • 72a8cf8dc   Move all command code into its own directory ... Browse Code »

    There are a lot of unrelated files in common, including all of the commands.
    Moving them into their own directory makes them easier to find and is more
    logical.

    Some commands include non-command code, such as cmd_scsi.c. This should be
    sorted out at some point so that the function can be enabled with or without
    the associated command.

    Unfortunately, with m68k I get this error:

    m68k: + M5329AFEE
    +arch/m68k/cpu/mcf532x/start.o: In function `_start':
    +arch/m68k/cpu/mcf532x/start.S:159:(.text+0x452): relocation truncated to fit: R_68K_PC16 against symbol `board_init_f' defined in .text.board_init_f section in common/built-in.o

    I hope someone can shed some light on what this means. I hope it isn't
    depending on the position of code in the image.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Acked-by: Stefan Roese
    Acked-by: Przemyslaw Marczak

    Simon Glass
     

20 Jan, 2016

1 commit

14 Jan, 2016

1 commit

  • f4db6c976   arm: mvebu: Add runtime detection of UART (xmodem) boot-mode ... Browse Code »
    58

    This patch adds runtime detection of the Marvell UART boot-mode (xmodem
    protocol). If this boot-mode is detected, SPL will return to the
    BootROM to continue the UART booting.

    With this patch its now possible, to generate a U-Boot image that
    can be booted either from the strapped boot-device (e.g. SPI NOR, MMC,
    etc) or via the xmodem protocol from the UART. In the UART case,
    the kwboot tool will dynamically insert the UART boot-device type
    into the image. And also patch the load address in the header, so
    that the mkimage header will be skipped (as its not expected by the
    Marvell BootROM).

    This simplifies the development for Armada XP / 38x based boards.
    As no special images need to be generated by selecting the
    MVEBU_BOOTROM_UARTBOOT Kconfig option.

    Since the Kconfig option MVEBU_BOOTROM_UARTBOOT is not needed any
    more, its now completely removed.

    Signed-off-by: Stefan Roese
    Cc: Luka Perkov
    Cc: Dirk Eibach
    Cc: Phil Sutter
    Cc: Kevin Smith

    Stefan Roese
     

12 Jan, 2016

1 commit

08 Jan, 2016

1 commit

05 Jan, 2016

1 commit

22 Dec, 2015

1 commit

08 Dec, 2015

1 commit

19 Nov, 2015

1 commit

  • 08598d6ee   ARM: zynq: Add target for building bootable SPL image for Zynq ... Browse Code »

    Add a build target to generate 'boot.bin' which includes SPL. This is
    used by the platforms BootROM to load SPL directly.

    This change also conditionally changes what the 'boot.bin' target
    generates depending on the SoC. Leaving the behaviour unchanged for the
    AT91 targets.

    Signed-off-by: Nathan Rossi
    Signed-off-by: Michal Simek
    Cc: Tom Rini
    Cc: Andreas Bießmann
    Cc: Heiko Schocher
    Reviewed-by: Tom Rini

    Nathan Rossi
     

17 Nov, 2015

1 commit

11 Nov, 2015

1 commit

10 Nov, 2015

2 commits

  • da58dec86   Various Makefiles: Add SPDX-License-Identifier tags ... Browse Code »
    40

    After consulting with some of the SPDX team, the conclusion is that
    Makefiles are worth adding SPDX-License-Identifier tags too, and most of
    ours have one. This adds tags to ones that lack them and converts a few
    that had full (or in one case, very partial) license blobs into the
    equivalent tag.

    Cc: Kate Stewart
    Signed-off-by: Tom Rini

    Tom Rini
     
  • 62e92077a   arm: support Thumb-1 with CONFIG_SYS_THUMB_BUILD ... Browse Code »

    When building a Thumb-1-only target with CONFIG_SYS_THUMB_BUILD,
    some files fail to build, most of the time because they include
    mcr instructions, which only exist for Thumb-2.

    This patch introduces a Kconfig option CONFIG_THUMB2 and uses
    it to select between Thumb-2 and ARM mode for the aforementioned
    files.

    Signed-off-by: Albert ARIBAUD

    Albert ARIBAUD
     

27 Oct, 2015

1 commit

  • 947cee112   arm: ls1021a: Add QSPI or IFC support in SD boot ... Browse Code »
    34

    As QSPI and IFC are pin-multiplexed on LS1021A, only IFC is supported in
    SD boot now. For the customer's demand, QSPI needs to be supported in SD
    boot too.

    This patch adds QSPI or IFC support in SD boot according to the
    corresponding defconfig. For detail, ls1021atwr_sdcard_ifc_defconfig is
    used to support IFC in SD boot and ls1021atwr_sdcard_qspi_defconfig is
    used to support QSPI in SD boot.

    Signed-off-by: Alison Wang
    Reviewed-by: York Sun

    Alison Wang
     

22 Oct, 2015

1 commit

21 Oct, 2015

3 commits

  • a34b46768   Makefile: Generate U_BOOT_DMI_DATE for SMBIOS ... Browse Code »

    Add U_BOOT_DMI_DATE (format mm/dd/yyyy) generation to be used by
    SMBIOS tables, as required by SMBIOS spec 3.0 [1]. See chapter 7.1,
    BIOS information structure offset 08h for details.

    [1] http://www.dmtf.org/sites/default/files/standards/documents/DSP0134_3.0.0.pdf

    Signed-off-by: Bin Meng
    Acked-by: Simon Glass

    Bin Meng
     
  • 9cffb2335   arm: mvebu: Add DM (driver model) support ... Browse Code »

    This patch adds driver model support for some Marvell MVEBU SoC's. Including
    Armada XP and 38x. All 3 currently mainlined boards are converted. DM is now
    selected automatically for MVEBU platforms.

    With this DM support now available for MVEBU, hardcoding the base addresses
    and other information is not necessary any more. Probing should be done
    by using the values provided via the device tree now instead. For this
    the driver also need to be converted to DM. Patches for some of the drivers
    will follow.

    Signed-off-by: Stefan Roese
    Cc: Simon Glass
    Cc: Luka Perkov

    Stefan Roese
     
  • 944c7a317   arm: mvebu: Add option to use UART xmodem protocol via kwboot ... Browse Code »
    1

    This patch enables the use of the kwboot tool, to boot mainline U-Boot
    on the Marvell Armada XP/38x SoC's. This is done by returning to the
    SoC's BootROM after SPL has initialized the SDRAM. We need to make sure
    to not reconfigure the internal register space and MBARs. Otherwise
    the BootROM will not be able to continue after SPL jumps back to it.

    To use this feature, please don't forget to change the BOOT_FROM line
    in your board specfic kwbimage.cfg file this way:

    BOOT_FROM uart

    Tested on these Marvell eval boards:
    DB-MV784MP-GP - Armada XP
    DB-88F6820-GP - Armada 38x

    Signed-off-by: Stefan Roese
    Cc: Dirk Eibach
    Cc: Kevin Smith
    Cc: Luka Perkov

    Stefan Roese
     

20 Oct, 2015

1 commit

12 Oct, 2015

1 commit

29 Sep, 2015

1 commit

07 Sep, 2015

1 commit

29 Aug, 2015

3 commits

  • 2d9efa122   Makefile: fix SOURCE_DATE_EPOCH for *BSD host ... Browse Code »

    The SOURCE_DATE_EPOCH mechanism for reproducible builds require some date(1)
    with -d switch to print the relevant date and time strings of another point of
    time.

    In other words it requires some date(1) that behaves like the GNU date(1) [1].
    The BSD date(1) [2] on the other hand has the same switch but with a different
    meaning.

    Respect this and check the date(1) abilities before usage, error on non
    working version. Use the well known pre- and suffixes for the GNU variant of
    a tool on *BSD hosts to search for a working date(1) version.

    [1] http://man7.org/linux/man-pages/man1/date.1.html [2]
    http://www.freebsd.org/cgi/man.cgi?query=date

    Signed-off-by: Andreas Bießmann

    Andreas Bießmann
     
  • cd43ddc01   ARM: keystone2: move the custom build rules out to keystone specific makefile ... Browse Code »

    Keystone has build rules introduced by commit ef509b9063fb7 ("k2hk: add
    support for k2hk SOC and EVM") and commit 0e7f2dbac6ead ("keystone: add
    support for NAND gpheader image").

    These are not reused by other platforms for the build, hence there is no
    clear benefit is maintaining them in the generic makefile as a build
    target. move these to the keystone specific make option

    Original idea of using config.mk by Lokesh Vutla

    Signed-off-by: Nishanth Menon
    Signed-off-by: Lokesh Vutla

    Nishanth Menon
     
  • 70d39f571   Makefile: Use correct timezone for U_BOOT_TZ ... Browse Code »

    When building with SOURCE_DATE_EPOCH the timezone is in UTC. When
    building normally the timezone is taken from the build machine's locale
    setting.

    Signed-off-by: Chris Packham
    Tested-by: Bin Meng
    Tested-by: Paul Kocialkowski
    Tested-by: Andreas Bießmann

    Chris Packham
     

26 Aug, 2015

1 commit

  • b09803238   x86: ifdtool: Support collating microcode into one place ... Browse Code »

    The Intel Firmware Support Package (FSP) requires that microcode be provided
    very early before the device tree can be scanned. We already support adding
    a pointer to the microcode data in a place where early init code can access.

    However this just points into the device tree and can only point to a single
    lot of microcode. For boards which may have different CPU types we must
    support multiple microcodes and pass all of them to the FSP in one place.

    Enhance ifdtool to scan all the microcode, place it together in the ROM and
    update the microcode pointer to point there. This allows us to pass multiple
    microcode blocks to the FSP using its existing API.

    Enable the flag in the Makefile so that this feature is used by default for
    all boards.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng
    Tested-by: Bin Meng

    Simon Glass
     

18 Aug, 2015

1 commit