Eric Lee / smarc-uboot

30 Jan, 2014

1 commit

  • 3d83efbce   sandbox: Use system headers first for sandbox's os.c in a different way ... Browse Code »

    Commit cbe5cdfcd changed config.mk and arch/sandbox/cpu/Makefile
    to use -idirafter instead of -I and remove -nostdinc.

    But
    * Sandbox-specific code dirties config.mk
    * os.c is compiled without such compiler flags as:
    -Wall -Wstrict-prototypes -Wno-format-security
    -fno-builtin -ffreestanding -fno-stack-protector
    -fstack-usage -Wno-format-nonliteral

    This commit use -idirafter and remove the -nostdinc
    differently and more simply.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

28 Jan, 2014

1 commit

27 Jan, 2014

2 commits

  • 0876703cf   boards.cfg: Keep the entries sorted ... Browse Code »

    Run "tools/reformat.py -i -d '-' -s 8 boards0.cfg && mv boards0.cfg boards.cfg"
    in order to keep the entries sorted.

    Signed-off-by: Fabio Estevam

    Fabio Estevam
     
  • 7395398ad   board_r - fixup functions table after relocation ... Browse Code »

    This is only required for "PIC" relocation and doesn't apply to modern
    "PIE" relocation which does data relocation as well as code.

    "init_sequence_r" is just an array that consists of compile-time
    adresses of init functions. Since this is basically an array of integers
    (pointers to "void" to be more precise) it won't be modified during
    relocation - it will be just copied to new location as it is.

    As a consequence on execution after relocation "initcall_run_list" will
    be jumping to pre-relocation addresses. As long as we don't overwrite
    pre-relocation memory area init calls are executed correctly. But still
    it is dangerous because after relocation we don't expect initially used
    memory to stay untouched.

    Cc: Tom Rini
    Cc: Masahiro Yamada
    Cc: Doug Anderson
    Cc: Thomas Langer
    Cc: Albert ARIBAUD
    Acked-by: Simon Glass
    Signed-off-by: Alexey Brodkin

    Alexey Brodkin
     

25 Jan, 2014

29 commits

23 Jan, 2014

3 commits

  • f28bea000   eSDHC: Calculate envaddr accroding to the address format ... Browse Code »

    On BSC9131, BSC9132, P1010 : For High Capacity SD Cards (> 2 GBytes), the
    32-bit source address specifies the memory address in block address
    format. Block length is fixed to 512 bytes as per the SD High Capacity
    specification. So we need to convert the block address format
    to byte address format to calculate the envaddr.

    If there is no enough space for environment variables or envaddr
    is larger than 4GiB, we relocate the envaddr to 0x400. The address
    relocated is in the front of the first partition that is assigned
    for sdboot only.

    Signed-off-by: Haijun Zhang
    Acked-by: Pantelis Antoniou
    Reviewed-by: York Sun

    Haijun.Zhang
     
  • d47e3d270   esdhc: Detecting 8 bit width before mmc initialization ... Browse Code »

    The upper 4 data signals of esdhc are shared with spi flash.
    So detect if the upper 4 pins are assigned to esdhc before
    enable sdhc 8 bit width.

    Signed-off-by: Haijun Zhang
    Acked-by: Pantelis Antoniou
    Reviewed-by: York Sun

    Haijun.Zhang
     
  • f7e27cc5e   esdhc: Workaround for card can't be detected on T4240QDS ... Browse Code »

    Card detection pin is ineffective on T4240QDS Rev1.0.
    There are two cards can be connected to board.
    1. eMMC card is built-in board, can not be removed. so
    For eMMC card it is always there.
    2. Card detecting pin is functional for SDHC card in Rev2.0.

    This workaround force sdhc driver scan and initialize the card
    regardless of whether the card is inserted or not in case Rev1.0.

    Signed-off-by: Haijun Zhang
    Acked-by: Pantelis Antoniou
    Reviewed-by: York Sun

    Haijun.Zhang
     

22 Jan, 2014

4 commits