Eric Lee / smarc-uboot

12 Apr, 2016

1 commit

22 Nov, 2015

1 commit

  • 354e3ed75   eeprom: Add bus argument to eeprom_init() ... Browse Code »

    Add bus argument to eeprom_init(), so that it can select
    the I2C bus number on which the eeprom resides. Any negative
    value of the $bus argument will preserve the old behavior.
    This is in place so that old code does not randomly break.

    Signed-off-by: Marek Vasut
    Cc: Simon Glass
    Cc: Tom Rini
    Cc: Heiko Schocher
    Reviewed-by: Heiko Schocher
    [trini: Wrap i2c_set_bus_num() call with CONFIG_SYS_I2C test]
    Signed-off-by: Tom Rini

    Marek Vasut
     

12 Oct, 2015

1 commit

  • e3cc5bc58   env_eeprom.c: Correct using saved environment ... Browse Code »

    The changes in ed6a5d4 unintentionally broke support for reading the
    environment saved to eeprom back. To correct this the crc-check and
    decision on which environment to use is now moved to env_relocate_spec.
    This is done for both the "redundant env" and the "single env" case.

    Signed-off-by: Ludger Dreier

    Ludger Dreier
     

06 Jun, 2014

1 commit

22 Mar, 2014

1 commit

  • 7ce1526ed   env: Add env_export() wrapper ... Browse Code »
    46

    Implement env_export() wrapper, so that all implementers of saveenv() don't
    have to call hexport_r(), crc32() etc. sequence . This trims down a bit of
    code duplication.

    Signed-off-by: Marek Vasut

    Marek Vasut
     

13 Jan, 2014

1 commit

  • 6d001e7df   env_eeprom - fix bus recovery for "eeprom_bus_read" ... Browse Code »

    "env_eeprom_bus" is no longer in use (it was introduced in commit
    548738b4d43af841ff58c787bce297ac6a8bf7d1 "cmd_eeprom: I2C updates").

    As in "eeprom_bus_write" we just reset I2C bus with the one we saved in
    "old_bus".

    Signed-off-by: Alexey Brodkin

    Cc: Wolfgang Denk
    Cc: Tom Rini
    Cc: Heiko Schocher

    Alexey Brodkin
     

15 Oct, 2013

1 commit

24 Jul, 2013

2 commits

23 Jul, 2013

2 commits

06 Apr, 2013

1 commit

03 Apr, 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
     

22 Nov, 2011

1 commit

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
     

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
     

05 Jul, 2010

1 commit

13 Mar, 2010

1 commit

18 Jan, 2010

2 commits

19 Oct, 2008

1 commit

11 Sep, 2008

3 commits

14 May, 2008

1 commit

12 May, 2008

1 commit

18 Apr, 2008

1 commit

01 Apr, 2006

1 commit

25 Sep, 2005

1 commit

28 Jun, 2003

1 commit

  • 8bde7f776   * Code cleanup: ... Browse Code »
    46

    - remove trailing white space, trailing empty lines, C++ comments, etc.
    - split cmd_boot.c (separate cmd_bdinfo.c and cmd_load.c)

    * Patches by Kenneth Johansson, 25 Jun 2003:
    - major rework of command structure
    (work done mostly by Michal Cendrowski and Joakim Kristiansen)

    wdenk
     

18 Sep, 2002

1 commit