Eric Lee / smarc-uboot

15 Oct, 2013

2 commits

  • 3765b3e7b   Coding Style cleanup: remove trailing white space ... Browse Code »

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     
  • 452a2722e   env_mmc: fix buffer allocation for armv7 ... Browse Code »
    46

    commit d196bd880347373237d73e0d115b4d51c68cf2ad adds
    redundand environment to mmc. The usage of malloc in
    env_relocate_spec triggers cache errors on armv7.

    Tested on a not mainlined i.MX53 board:

    Board: TQMa53
    I2C: ready
    DRAM: 512 MiB
    MMC: FSL_SDHC: 0, FSL_SDHC: 1
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f57c2d8
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f57e2d8
    ERROR: v7_dcache_inval_range - start address is not aligned - 0x8f57e2e0
    ERROR: v7_dcache_inval_range - stop address is not aligned - 0x8f5802e0
    Using default environment

    Signed-off-by: Markus Niebel

    Markus Niebel
     

24 Jul, 2013

1 commit

14 Jun, 2013

1 commit

  • 5c088ee84   env_mmc: allow negative CONFIG_ENV_OFFSET ... Browse Code »
    29

    A negative value of CONFIG_ENV_OFFSET is treated as a backwards offset
    from the end of the eMMC device/partition, rather than a forwards offset
    from the start.

    This is useful when a single board may be stuffed with different eMMC
    devices, each of which has a different capacity, and you always want the
    environment to be stored at the very end of the device (or eMMC boot
    partition for example).

    One example of this case is NVIDIA's Ventana reference board.

    Signed-off-by: Stephen Warren
    Signed-off-by: Andy Fleming

    Stephen Warren
     

02 May, 2013

1 commit

06 Apr, 2013

1 commit

03 Apr, 2013

1 commit

04 Feb, 2013

1 commit

14 Dec, 2012

1 commit

  • be11235ab   env: Hide '.' variables in env print by default ... Browse Code »

    When printing all variables with env print, don't print variables that
    begin with '.'. If env print is called with a '-a' switch, then
    include variables that begin with '.' (just like the ls command).

    Variables printed explicitly will be printed even without the -a.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     

06 Sep, 2012

1 commit

  • 9404a5fc7   env_mmc: allow environment to be in an eMMC partition ... Browse Code »

    eMMC devices may have hardware-level partitions: 2 boot partitions,
    up to 4 general partitions, plus the user area. This change introduces
    optional config variable CONFIG_SYS_MMC_ENV_PART to indicate which
    partition the environment should be stored in: 0=user, 1=boot0, 2=boot1,
    4..7=general0..3. This allows the environment to be kept out of the user
    area, which simplifies the management of OS-/user-level (MBR/GPT)
    partitions within the user area.

    Signed-off-by: Stephen Warren
    Signed-off-by: Andy Fleming

    Stephen Warren
     

07 Jul, 2012

1 commit

05 Jan, 2012

1 commit

22 Nov, 2011

3 commits

08 Nov, 2011

1 commit

  • 37f2fe747   env: allow to export only selected variables ... Browse Code »

    New syntax:
    env export [-t | -b | -c] [-s size] addr [var ...]

    With this change it is possible to provide a list of variables names
    that shall be exported. Whenno arguments are given, the whole
    environment gets exported.

    NOTE: The new handling of the "size" argument means a change to the
    user API.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

05 Apr, 2011

1 commit

  • 97039ab98   env_mmc: Allow board code to override the environment address ... Browse Code »

    On some boards the environment may not be located at a fixed address in
    the MMC/SDHC card. This allows those boards to implement their own
    means to report what address the environment is located at.

    Signed-off-by: Mingkai Hu
    Signed-off-by: Jerry Huang
    Signed-off-by: Zhao Chenhui
    Acked-by: Andy Fleming
    Signed-off-by: Kumar Gala

    Mingkai Hu
     

18 Dec, 2010

1 commit

  • 2eb1573f0   hashtable: drop all non-reentrant versions ... Browse Code »

    The non-reentrant versions of the hashtable functions operate on a single
    shared hashtable. So if two different people try using these funcs for
    two different purposes, they'll cause problems for the other.

    Avoid this by converting all existing hashtable consumers over to the
    reentrant versions and then punting the non-reentrant ones.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

15 Nov, 2010

1 commit

  • 6d1d51b32   env_mmc: fix compile warning ... Browse Code »

    hexport would complain implicit declaration, if we don't add the
    include file.

    env_mmc.c: In function 'saveenv':
    env_mmc.c:109: warning: implicit declaration of function 'hexport'

    Signed-off-by: Lei Wen

    Lei Wen
     

18 Oct, 2010

1 commit

14 Oct, 2010

2 commits

  • e79f48393   env_mmc: fix cannot save env issue ... Browse Code »

    The env change its implementation after this log, while env mmc
    didn't change it immediately, which cause issue. Follow to the
    new style to fix it.

    commit ea882baf9c17cd142c99e3ff640d3ab01daa5cec
    Author: Wolfgang Denk
    Date: Sun Jun 20 23:33:59 2010 +0200

    New implementation for internal handling of environment variables.

    Signed-off-by: Lei Wen

    Lei Wen
     
  • d470a6f60   env_mmc: Fix crashing bug encountered after enabling ARM relocation ... Browse Code »

    The crash was occuring in env_relocate because it was being called prior
    to mmc_initialize. This patch moves the MMC initialization earlier in
    the init process.

    This patch also cleans up the env_relocate_spec code in env_mmc.c

    Signed-off-by: Steve Sakoman
    Acked-by: Stefano Babic

    Steve Sakoman
     

07 Oct, 2010

1 commit

19 Sep, 2010

1 commit