Eric Lee / smarc-uboot

03 May, 2016

1 commit

25 Mar, 2016

2 commits

25 Feb, 2016

5 commits

  • 05195b2cb   Merge git://git.denx.de/u-boot-dm Browse Code »
    Tom Rini
     
  • 070b781b2   patman: fix series-notes handling for buildman ... Browse Code »

    A patman series with a 'Series-notes' section causes
    buildman to crash with:

    self.series.notes += self.section
    TypeError: cannot concatenate 'str' and 'list' objects

    Fix by initializing series.notes as a one-element array
    rather than a scalar.

    Signed-off-by: Albert ARIBAUD
    Acked-by: Simon Glass
    Tested-by: Simon Glass

    Albert ARIBAUD
     
  • e8aebc474   tools: Update openrisc toolchain information ... Browse Code »

    Since commit 87da2690ab81b5f29f83dc85c55f933e6ef414bc
    "openrisc: updating build tools naming convention", openrisc
    kernel.org toolchain is out of date and cannot build U-Boot.
    Update buildman and moveconfig tools to refer to the new one.

    Signed-off-by: Bin Meng

    Bin Meng
     
  • c6e3e8213   tools: -Wno-deprecated-declarations for OpenSSL on darwin ... Browse Code »

    Since OpenSSL is deprecated on OS X in favour of Common Crypto API disable the
    warning for this host OS.

    Another solution would be to add some glue layer for crypto stuff, but I think
    this is not worth the effort.

    Signed-off-by: Andreas Bießmann
    Reviewed-by: Simon Glass

    Andreas Bießmann
     
  • c190fbd01   Gracefully handle 64-bit signed-extended 32-bit Load addresses ... Browse Code »

    To follow the MIPS 32-bit and 64-bit memory map conventions (*) recent
    MIPS Linux kernels are using a 64-bit sign extended value
    (0xffffffff80010000) for the 32-bit load address (0x80010000) of the
    Creator CI20 board kernel. When this 64-bit argument was passed to
    mkimage running on a 32-bit machine such as the Creator CI20 board the
    load address was incorrectly formed from the upper 32-bit sign-extend
    bits (0xffffffff) by the strtoul instead of from the lower 32-bits
    (0x80010000). The mkimage should be able to tolerate the longer
    sign-extended 64-bit version of the 32-bit arguments with the use of
    strtoull. Use of the strtoll in place of the strtol in mkimage.c
    resolves the issue of self hosted kernel builds for the Creator CI20
    board (+) and (++).

    (*) http://techpubs.sgi.com/library/dynaweb_docs/0620/SGI_Developer/books/DevDriver_PG/sgi_html/ch01.html
    (+) https://github.com/MIPS/CI20_linux/issues/23
    (++) https://github.com/MIPS/CI20_linux/issues/22

    Signed-off-by: William Cohen

    William Cohen
     

21 Feb, 2016

2 commits

08 Feb, 2016

8 commits

06 Feb, 2016

1 commit

  • a187559e3   Use correct spelling of "U-Boot" ... Browse Code »

    Correct spelling of "U-Boot" shall be used in all written text
    (documentation, comments in source files etc.).

    Signed-off-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Reviewed-by: Simon Glass
    Reviewed-by: Minkyu Kang

    Bin Meng
     

03 Feb, 2016

1 commit

  • 276d3ebb8   tools: mxsboot: Use more portable cpu_to_le32() ... Browse Code »
    34

    Currently when building mxsboot on certain machines it reports:

    HOSTCC tools/mxsboot
    tools/mxsboot.c: In function 'mx28_create_sd_image':
    tools/mxsboot.c:560: warning: implicit declaration of function 'htole32'
    /tmp/cchLIV6q.o: In function 'main':
    mxsboot.c:(.text+0x6d8): undefined reference to 'htole32'
    mxsboot.c:(.text+0x6e7): undefined reference to 'htole32'
    mxsboot.c:(.text+0x6f6): undefined reference to 'htole32'
    mxsboot.c:(.text+0x705): undefined reference to 'htole32'
    mxsboot.c:(.text+0x711): undefined reference to 'htole32'
    /tmp/cchLIV6q.o:mxsboot.c:(.text+0x71d): more undefined references to
    'htole32' follow
    collect2: ld returned 1 exit status
    make[1]: *** [tools/mxsboot] Error 1
    make: *** [tools] Error 2

    The solution is to use cpu_to_le32() instead which is more portable,
    just like other U-Boot tools [1] do.

    [1] http://lists.denx.de/pipermail/u-boot/2014-October/192919.html

    Suggested-by: Marek Vasut
    Signed-off-by: Bin Meng
    Acked-by: Marek Vasut

    Bin Meng
     

22 Jan, 2016

1 commit

21 Jan, 2016

2 commits

  • 747440d0f   dm: video: test: Test that bitmap display works correctly ... Browse Code »

    Add a test for the 'bmp' command. Test both the uncompressed and compressed
    versions of the file, since they use different code paths.

    Signed-off-by: Simon Glass
    Acked-by: Anatolij Gustschin

    Simon Glass
     
  • 27067a46c   patman: Add --thread option ... Browse Code »

    Add option to create threaded series of patches.
    With it, it will be possible to create patch threads like this:
    [PATCH 0/10] Add support for time travel
    [PATCH 1/10] Add Flux Capacitor driver
    [PATCH 2/10] Add Mr. Fusion driver
    (...)

    Internally it will call git send-email with --thread option

    Signed-off-by: Mateusz Kulikowski
    Acked-by: Simon Glass

    Mateusz Kulikowski
     

15 Jan, 2016

1 commit

14 Jan, 2016

2 commits

  • 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
     
  • 81e33f4b6   arm: mvebu: Move SoC selection (A38X vs AXP) into Kconfig ... Browse Code »

    Until now, the SoC selection for the ARCH_MVEBU platforms has been done
    in the config header. Using CONFIG_ARMADA_XP in a non-clear way. As
    it needed to get selected for AXP and A38x based boards. This patch
    now changes this to move the SoC selection to Kconfig. And also
    uses CONFIG_ARCH_MVEBU as a common define for both AXP and A38x.
    This makes things a bit clearer - especially for new board additions.

    Additionally the defines CONFIG_SYS_MVEBU_DDR_AXP and
    CONFIG_SYS_MVEBU_DDR_A38X are replaced with the already available
    CONFIG_ARMADA_38X and CONFIG_ARMADA_XP.

    And CONFIG_DDR3 is removed, as its not referenced anywhere.

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

    Stefan Roese
     

13 Jan, 2016

1 commit

08 Jan, 2016

2 commits

18 Dec, 2015

1 commit

17 Dec, 2015

1 commit

14 Dec, 2015

3 commits

11 Dec, 2015

1 commit

08 Dec, 2015

1 commit

  • 346331412   mkimage: Fix warning from fix for generating multi and script images again ... Browse Code »

    Seems 6ae6e160 broke creating images in certain cases, there
    are two problems with that patch.

    First is that the expression "!x == 4 || !x == 6" is ambiguous. The
    intention here was "!(x == 4) || !(x == 6)" based on reading further in
    the file, where this was borrowed from. This however is interpreted by
    gcc as "(!x) == 4 || (!x) == 6" and always false. gcc-5.x will warn
    about this case.

    The second problem is that we do not want to test for the case of "(NOT x
    is 4) OR (NOT x is 6)" but instead "(x is not equal to 4) AND (x is not
    equal to 6)". This is because in those two cases we already execute the
    code question in another part of the file. Rewrite the expression and
    add parenthesis for clarity.

    Signed-off-by: Marek Vasut
    Cc: Tom Rini
    Cc: Philippe De Swert
    Cc: Simon Glass
    [trini: Re-word Marek's explanation]

    Marek Vasut
     

06 Dec, 2015

1 commit

  • 6ae6e1600   mkimage : Fix generating multi and script images ... Browse Code »
    34

    Seems 92a655c3 broke creating multi and script type images.
    Since the file1:file2:file3 string does not get split up,
    it fails on trying to open an non-existing file.

    mkimage -A arm -O linux -T multi -C none -d zImage:splash.bmp:device.dtb uimage
    tools/mkimage: Can't open zImage:splash.bmp:device.dtb: No such file or directory

    Since the sizes of the different parts seem to get added in the actual
    routine that handles multi and script type images, we can probably skip the
    bit of the code that causes the failure for that type of images.

    Signed-off-by: Philippe De Swert

    Philippe De Swert
     

01 Dec, 2015

2 commits

  • 3641339ef   rockchip: Add support for rk's second level loader ... Browse Code »

    The Rockchip boot ROM could load & run an initial spl loader,
    and continue to load a second level boot-loader(which stored
    right after the initial loader) when it returns.
    Modify idblock generation code to support it.

    Signed-off-by: Jeffy Chen
    Acked-by: Simon Glass

    Jeffy Chen
     
  • 6ae586094   rockchip: Add max spl size & spl header configs ... Browse Code »

    Our chips may have different max spl size and spl header, so
    we need to add configs for that.

    Signed-off-by: Jeffy Chen
    Acked-by: Simon Glass
    Dropped CONFIG_ROCKCHIP_MAX_SPL_SIZE from rk3288_common.h,
    Added $(if...) to tools/Makefile to fix widespread build breakage
    Signed-off-by: Simon Glass

    Series-changes: 8
    - Drop CONFIG_ROCKCHIP_MAX_SPL_SIZE from rk3288_common.h,
    - Add $(if...) to tools/Makefile to fix widespread build breakage

    Jeffy Chen
     

29 Nov, 2015

1 commit

  • 76b391cde   tools/kwbimage: fix size computations for v1 images ... Browse Code »

    Fix computation of haeder size and binary header size.
    Size of opt header and some 32bit values were not taken into account. This could
    result in invalid boot images (due to the wrong binary header size, the image could
    claim to have another extension header after the binary extension although there
    is none).

    Use "uint32_t" instead of "unsigned int" for header size computation.

    Signed-off-by: Reinhard Pfau
    Reviewed-by: Stefan Roese
    Cc: Luka Perkov

    Reinhard Pfau