13 Dec, 2013

7 commits

  • The build rules of
    - include/autoconf.mk.dep
    - include/autoconf.mk
    - include/spl-autoconf.mk
    - include/tpl-autoconf.mk
    were not nice.

    They created empty files (which are never updated)
    if an error occurs during preprocessing.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • Add a test for dumpimage.

    Signed-off-by: Guilherme Maciel Ferreira
    Signed-off-by: Simon Glass

    Guilherme Maciel Ferreira
     
  • Given a multi-file image created through the mkimage's -d option:

    $ mkimage -A x86 -O linux -T multi -n x86 -d vmlinuz:initrd.img:System.map \
    multi.img

    Image Name: x86
    Created: Thu Jul 25 10:29:13 2013
    Image Type: Intel x86 Linux Multi-File Image (gzip compressed)
    Data Size: 13722956 Bytes = 13401.32 kB = 13.09 MB
    Load Address: 00000000
    Entry Point: 00000000
    Contents:
    Image 0: 4040128 Bytes = 3945.44 kB = 3.85 MB
    Image 1: 7991719 Bytes = 7804.41 kB = 7.62 MB
    Image 2: 1691092 Bytes = 1651.46 kB = 1.61 MB

    It is possible to perform the innverse operation -- extracting any file from
    the image -- by using the dumpimage's -i option:

    $ dumpimage -i multi.img -p 2 System.map

    Although it's feasible to retrieve "data files" from image through scripting,
    the requirement to embed tools such 'dd', 'awk' and 'sed' for this sole purpose
    is cumbersome and unreliable -- once you must keep track of file sizes inside
    the image. Furthermore, extracting data files using "dumpimage" tool is faster
    than through scripting.

    Signed-off-by: Guilherme Maciel Ferreira
    Signed-off-by: Simon Glass

    Guilherme Maciel Ferreira
     
  • In order to avoid duplicating code and keep only one point of modification,
    the functions, structs and defines useful for "dumpimage" were moved from
    "mkimage" to a common module called "imagetool".

    This modification also weakens the coupling between image types (FIT, IMX, MXS,
    and so on) and image tools (mkimage and dumpimage). Any tool may initialize the
    "imagetool" through register_image_tool() function, while the image types
    register themselves within an image tool using the register_image_type()
    function:

    +---------------+
    +------| fit_image |
    +--------------+ +-----------+ | +---------------+
    | mkimage |--------> | | | |
    Signed-off-by: Simon Glass

    Guilherme Maciel Ferreira
     
  • This function should be declared static.

    Signed-off-by: Guilherme Maciel Ferreira
    Signed-off-by: Simon Glass

    Guilherme Maciel Ferreira
     
  • The last users of CONFIG_KGDB_SER_INDEX were removed more than 3 years
    ago in commits 550650ddd0 and bf16500f79, either kgdb subsystem should
    care about this parameter or it should be gone completely.

    Signed-off-by: Vladimir Zapolskiy

    Vladimir Zapolskiy
     
  • For LPC32XX high-speed UART it is required to send a carriage return
    symbol along with line feed. The problem was introduced in e503f90a
    commit.

    Signed-off-by: Vladimir Zapolskiy
    Cc: Marek Vasut
    Acked-by: Marek Vasut

    Vladimir Zapolskiy
     

12 Dec, 2013

4 commits


11 Dec, 2013

2 commits


10 Dec, 2013

11 commits


09 Dec, 2013

7 commits


08 Dec, 2013

4 commits

  • Faraday FTSDC021 is a controller which is compliant with
    SDHCI v3.0, SDIO v2.0 and MMC v4.3.

    However this driver is only verified with SD memory cards.

    Signed-off-by: Kuo-Jung Su
    Acked-by: Pantelis Antoniou
    CC: Andy Fleming

    Kuo-Jung Su
     
  • Existing eSDHC SPL framework assumes booting from sd-image
    with boot_format header which contains final u-boot Image
    offset and size. No such header is present in case of
    corenet devices like T1040 as corenet deivces use PBI-RCW
    based intialization.

    So, for corenet deives, SPL bootloader use values provided
    at compilation time. These values can be defined in board
    specific config file.

    Signed-off-by: Priyanka Jain
    Acked-by: Pantelis Antoniou

    Priyanka Jain
     
  • If platform provides "host->fifoth_val" it will be used for
    initialization of DWMCI_FIFOTH register. Otherwise default value will be
    used.

    This implementation allows:
    * escape unclear and recursive calculations that are currently in use
    * use whatever custom value for DWMCI_FIFOTH initialization if any
    particular SoC requires it

    Signed-off-by: Alexey Brodkin

    Cc: Mischa Jonker
    Cc: Alim Akhtar
    Cc: Rajeshwari Shinde
    Cc: Jaehoon Chung
    Cc: Amar
    Cc: Kyungmin Park
    Cc: Minkyu Kang
    Cc: Simon Glass
    Cc: Pantelis Antoniou
    Cc: Andy Fleming
    Acked-by: Jaehoon Chung
    Acked-by: Pantelis Antoniou

    Alexey Brodkin
     
  • dw-mmc.c is the general driver file.
    So, remove the exynos specific code at dw-mmc.c.
    Instead, exynos specific cod can be move into exynos-dw_mmc.c.

    Signed-off-by: Jaehoon Chung
    Acked-by: Alexey Brodkin
    Acked-by: Pantelis Antoniou
    Acked-by: Minkyu Kang

    Jaehoon Chung
     

07 Dec, 2013

2 commits

  • Current LDS files /DISCARD/ a lot of sections when linking ELF
    files, causing diagnostic tools such as readelf or objdump to
    produce partial output. Keep all section at link stage, filter
    only at objcopy time so that .bin remains minimal.

    Signed-off-by: Albert ARIBAUD
    Reviewed-by: Benoît Thébaudeau

    Albert ARIBAUD
     
  • The lower 5 bit of MVBAR is UNK/SBZP.
    So, Monitor Vector Base Address must be 32-byte aligned.
    On the other hand, the secure monitor handler does not need
    32-byte alignment.

    This commit moves ".algin 5" directive to the correct place.

    Signed-off-by: Masahiro Yamada
    Cc: Andre Przywara
    Acked-by: Andre Przywara

    Masahiro Yamada
     

06 Dec, 2013

3 commits