Eric Lee / smarc-uboot

24 Jul, 2013

1 commit

14 Jun, 2013

1 commit

  • 5707df779   mmc: fix env in mmc with redundant compile error ... Browse Code »

    The commit d196bd8 (env_mmc: add support for redundant environment)
    introduce the following compile error when enable redundant
    environment support with MMC
    ---88---

    Add this patch to fix it

    Signed-off-by: Bo Shen
    Reviewed-by: Michael Heimpold
    Signed-off-by: Andy Fleming

    Bo Shen
     

12 Apr, 2013

2 commits

14 Dec, 2012

4 commits

19 Sep, 2012

2 commits

  • b64b7c3df   env: make "env default" selective, check and apply ... Browse Code »

    Change the syntax (user API) for "env default":
    -f: override write-once variables
    var... : accept individual variable(s)
    -a: all (resetting the whole env is NOT the default behavior)

    Enable variable checking and make changes effective by
    enabling do_apply argument to himport_r().

    Signed-off-by: Gerlando Falauto

    Gerlando Falauto
     
  • c5983592e   env: add check/apply logic to himport_r() ... Browse Code »

    Change hashtable so that a callback function will decide whether a
    variable can be overwritten, and possibly apply the changes.

    So add a new field to struct hsearch_data:

    o "apply" callback function to check whether a variable can be
    overwritten, and possibly immediately apply the changes;
    when NULL, no check is performed.

    And a new argument to himport_r():
    o "do_apply": whether to call the apply callback function

    NOTE: This patch does not change the current behavior.

    Signed-off-by: Gerlando Falauto
    Reviewed-by: Marek Vasut

    Gerlando Falauto
     

22 Jun, 2012

1 commit

05 Jan, 2012

1 commit

22 Nov, 2011

5 commits

01 Aug, 2011

1 commit

26 Jul, 2011

1 commit

16 Feb, 2011

1 commit

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
     

20 Sep, 2010

1 commit

  • ea882baf9   New implementation for internal handling of environment variables. ... Browse Code »

    Motivation:

    * Old environment code used a pessimizing implementation:
    - variable lookup used linear search => slow
    - changed/added variables were added at the end, i. e. most
    frequently used variables had the slowest access times => slow
    - each setenv() would calculate the CRC32 checksum over the whole
    environment block => slow
    * "redundant" envrionment was locked down to two copies
    * No easy way to implement features like "reset to factory defaults",
    or to select one out of several pre-defined (previously saved) sets
    of environment settings ("profiles")
    * No easy way to import or export environment settings

    ======================================================================

    API Changes:

    - Variable names starting with '#' are no longer allowed

    I didn't find any such variable names being used; it is highly
    recommended to follow standard conventions and start variable names
    with an alphanumeric character

    - "printenv" will now print a backslash at the end of all but the last
    lines of a multi-line variable value.

    Multi-line variables have never been formally defined, allthough
    there is no reason not to use them. Now we define rules how to deal
    with them, allowing for import and export.

    - Function forceenv() and the related code in saveenv() was removed.
    At the moment this is causing build problems for the only user of
    this code (schmoogie - which has no entry in MAINTAINERS); may be
    fixed later by implementing the "env set -f" feature.

    Inconsistencies:

    - "printenv" will '\\'-escape the '\n' in multi-line variables, while
    "printenv var" will not do that.

    ======================================================================

    Advantages:

    - "printenv" output much better readable (sorted)
    - faster!
    - extendable (additional variable properties can be added)
    - new, powerful features like "factory reset" or easy switching
    between several different environment settings ("profiles")

    Disadvantages:

    - Image size grows by typically 5...7 KiB (might shrink a bit again on
    systems with redundant environment with a following patch series)

    ======================================================================

    Implemented:

    - env command with subcommands:

    - env print [arg ...]

    same as "printenv": print environment

    - env set [-f] name [arg ...]

    same as "setenv": set (and delete) environment variables

    ["-f" - force setting even for read-only variables - not
    implemented yet.]

    - end delete [-f] name

    not implemented yet

    ["-f" - force delete even for read-only variables]

    - env save

    same as "saveenv": save environment

    - env export [-t | -b | -c] addr [size]

    export internal representation (hash table) in formats usable for
    persistent storage or processing:

    -t: export as text format; if size is given, data will be
    padded with '\0' bytes; if not, one terminating '\0'
    will be added (which is included in the "filesize"
    setting so you can for exmple copy this to flash and
    keep the termination).
    -b: export as binary format (name=value pairs separated by
    '\0', list end marked by double "\0\0")
    -c: export as checksum protected environment format as
    used for example by "saveenv" command
    addr: memory address where environment gets stored
    size: size of output buffer

    With "-c" and size is NOT given, then the export command will
    format the data as currently used for the persistent storage,
    i. e. it will use CONFIG_ENV_SECT_SIZE as output block size and
    prepend a valid CRC32 checksum and, in case of resundant
    environment, a "current" redundancy flag. If size is given, this
    value will be used instead of CONFIG_ENV_SECT_SIZE; again, CRC32
    checksum and redundancy flag will be inserted.

    With "-b" and "-t", always only the real data (including a
    terminating '\0' byte) will be written; here the optional size
    argument will be used to make sure not to overflow the user
    provided buffer; the command will abort if the size is not
    sufficient. Any remainign space will be '\0' padded.

    On successful return, the variable "filesize" will be set.
    Note that filesize includes the trailing/terminating '\0'
    byte(s).

    Usage szenario: create a text snapshot/backup of the current
    settings:

    => env export -t 100000
    => era ${backup_addr} +${filesize}
    => cp.b 100000 ${backup_addr} ${filesize}

    Re-import this snapshot, deleting all other settings:

    => env import -d -t ${backup_addr}

    - env import [-d] [-t | -b | -c] addr [size]

    import external format (text or binary) into hash table,
    optionally deleting existing values:

    -d: delete existing environment before importing;
    otherwise overwrite / append to existion definitions
    -t: assume text format; either "size" must be given or the
    text data must be '\0' terminated
    -b: assume binary format ('\0' separated, "\0\0" terminated)
    -c: assume checksum protected environment format
    addr: memory address to read from
    size: length of input data; if missing, proper '\0'
    termination is mandatory

    - env default -f

    reset default environment: drop all environment settings and load
    default environment

    - env ask name [message] [size]

    same as "askenv": ask for environment variable

    - env edit name

    same as "editenv": edit environment variable

    - env run

    same as "run": run commands in an environment variable

    ======================================================================

    TODO:

    - drop default env as implemented now; provide a text file based
    initialization instead (eventually using several text files to
    incrementally build it from common blocks) and a tool to convert it
    into a binary blob / object file.

    - It would be nice if we could add wildcard support for environment
    variables; this is needed for variable name auto-completion,
    but it would also be nice to be able to say "printenv ip*" or
    "printenv *addr*"

    - Some boards don't link any more due to the grown code size:
    DU405, canyonlands, sequoia, socrates.

    => cc: Matthias Fuchs ,
    Stefan Roese ,
    Heiko Schocher

    - Dropping forceenv() causes build problems on schmoogie

    => cc: Sergey Kubushyn

    - Build tested on PPC and ARM only; runtime tested with NOR and NAND
    flash only => needs testing!!

    Signed-off-by: Wolfgang Denk
    Cc: Matthias Fuchs ,
    Cc: Stefan Roese ,
    Cc: Heiko Schocher
    Cc: Sergey Kubushyn

    Wolfgang Denk
     

13 Jul, 2010

1 commit

  • c9f7351b5   NAND: environment offset in OOB (CONFIG_ENV_OFFSET_OOB) ... Browse Code »

    This is a re-submission of the patch by Harald Welte
    with minor modifications for rebase and changes
    as suggested by Scott Wood [1] [2].

    This patch enables the environment partition to have a run-time dynamic
    location (offset) in the NAND flash. The reason for this is simply that
    all NAND flashes have factory-default bad blocks, and a fixed compile
    time offset would mean that sometimes the environment partition would
    live inside factory bad blocks. Since the number of factory default
    blocks can be quite high (easily 1.3MBytes in current standard
    components), it is not economic to keep that many spare blocks inside
    the environment partition.

    With this patch and CONFIG_ENV_OFFSET_OOB enabled, the location of the
    environment partition is stored in the out-of-band (OOB) data of the
    first block in flash. Since the first block is where most systems boot
    from, the vendors guarantee that the first block is not a factory
    default block.

    This patch introduces the 'nand env.oob' command, which can be called
    from the u-boot command line. 'nand env.oob get' reads the address of
    the environment partition from the OOB data, 'nand env.oob set
    {offset,partition-name}' allows the setting of the marker by specifying
    a numeric offset or a partition name.

    [1] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/43916
    [2] http://article.gmane.org/gmane.comp.boot-loaders.u-boot/79195

    Signed-off-by: Ben Gardiner
    Acked-by: Harald Welte

    Ben Gardiner
     

05 Jul, 2010

1 commit

25 Aug, 2009

1 commit

  • 0a9e4e772   unify {CONFIG_,}ENV_IS_EMBEDDED ... Browse Code »

    Some boards have fallen out of sync by defining CONFIG_ENV_IS_EMBEDDED
    manually. While it is useful to have this available to the build system,
    let's do it automatically rather than forcing people to opt into it.

    Signed-off-by: Mike Frysinger
    Signed-off-by: Albin Tonnerre
    Signed-off-by: Wolfgang Denk

    Mike Frysinger
     

20 Jul, 2009

1 commit

  • 375660907   compiler.h: unify system ifdef cruft here ... Browse Code »

    Shove a lot of the HOSTCC and related #ifdef checking crap into the new
    compiler.h header so that we can keep all other headers nice and clean.

    Also introduce custom uswap functions so we don't have to rely on the non
    standard implementations that a host may (or may not in the case of OS X)
    provide. This allows mkimage to finally build cleanly on an OS X system.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

04 Apr, 2009

1 commit

  • 75eb82ec7   mflash: Initial mflash support ... Browse Code »

    Mflash is fusion memory device mainly targeted consumer eletronic and
    mobile phone.
    Internally, it have nand flash and other hardware logics and supports
    some different operation (ATA, IO, XIP) modes.

    IO mode is custom mode for the host that doesn't have IDE interface.
    (Many mobile targeted SoC doesn't have IDE bus)

    This driver support mflash IO mode.

    Followings are brief descriptions about IO mode.

    1. IO mode based on ATA protocol and uses some custom command. (read
    confirm, write confirm)
    2. IO mode uses SRAM bus interface.

    Signed-off-by: unsik Kim

    unsik Kim
     

19 Oct, 2008

1 commit

11 Sep, 2008

3 commits

10 Jul, 2008

2 commits

15 May, 2008

1 commit

14 May, 2008

1 commit

24 Apr, 2008

1 commit

  • 89cdab788   crc32: use uint32_t rather than unsigned long ... Browse Code »

    The envcrc.c does sizeof(unsigned long) when calculating the crc, but
    this is done with the build toolchain instead of the target tool
    chain, so if the build is a 64bit system but the target is 32bits,
    the size will obviously be wrong. This converts all unsigned long
    stuff related to crc32 to uint32_t types. Compile tested only: output
    of ./tools/envcrc when run on a 32bit build system matches that of a
    64bit build system.

    Signed-off-by: Mike Frysinger
    Acked-by: Jean-Christophe PLAGNIOL-VILLARD

    Mike Frysinger
     

28 Nov, 2006

1 commit

13 Sep, 2006

1 commit

21 Mar, 2006

1 commit

06 Mar, 2003

1 commit