15 Oct, 2013

1 commit


24 Jul, 2013

1 commit


14 Dec, 2012

1 commit

  • 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
     

05 Jan, 2012

1 commit


22 Nov, 2011

3 commits


08 Nov, 2011

1 commit

  • 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
     

26 Jul, 2011

1 commit


18 Dec, 2010

1 commit

  • 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
     

24 Oct, 2010

1 commit

  • With debug the follow is printed:
    => saveenv
    Saving Environment to Flash...
    Data to save 0x18000
    Data (start 0xfff48000, len 0x18000) saved at 0x7fe63f20
    Protect off FFF40000 ... FFF5FFFF
    Un-Protected 1 sectors
    Erasing Flash...
    . done
    Erased 1 sectors
    Writing to Flash... Restoring the rest of data to 0xfff48000 len 0x18000
    done
    Protected 1 sectors
    =>

    Without debug:
    => saveenv
    Saving Environment to Flash...
    Un-Protected 1 sectors
    Erasing Flash...
    . done
    Erased 1 sectors
    Writing to Flash... done
    Protected 1 sectors
    =>

    Signed-off-by: Peter Tyser

    Peter Tyser
     

20 Sep, 2010

1 commit

  • 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

2 commits


10 Aug, 2009

1 commit

  • The only environment type that uses this variable is spi flash, and that is
    only because it is reimplementing the common set_default_env() function.
    So fix the spi flash code and kill off the default_environment_size in the
    process.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

18 Feb, 2009

1 commit


11 Sep, 2008

3 commits


04 May, 2008

1 commit

  • If you enable environment in the flash, but disable the embedded
    option, and you disable the saveenv command, then the #if nested
    logic will trigger a compile failure:
    env_flash.c: In function 'env_relocate_spec':
    env_flash.c:399: error: 'flash_addr' undeclared (first use in this function)
    The fix is to add CMD_SAVEENV ifdef protection like everywhere else.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

29 Aug, 2007

1 commit


11 Jul, 2007

1 commit


09 Jul, 2007

1 commit


04 Jul, 2007

1 commit


01 Apr, 2006

1 commit


13 Oct, 2005

1 commit


10 Jan, 2005

1 commit


14 Mar, 2004

2 commits

  • Fix problems with GCC 3.3.x which changed handling of global
    variables explicitly initialized to zero (now in .bss instead of
    .data as before).

    * Patch by Leon Kukovec, 02 Mar 2004:
    add strswab() to fix IDE LBA capacity, firmware and model numbers
    on little endian machines

    * Patch by Masami Komiya, 02 Mar 2004:
    - Remove get_ticks() from NFS code
    - Add verification of RPC transaction ID

    * Patch by Pierre Aubert, 02 Mar 2004:
    cleanup for IDE and USB drivers for MPC5200

    wdenk
     
  • - Added LBA48 support (CONFIG_LBA48 & CFG_64BIT_LBA)
    - Added support for 64bit printing in vsprintf (CFG_64BIT_VSPRINTF)
    - Added support for 64bit strtoul (CFG_64BIT_STRTOUL)

    * Patch by Masami Komiya, 27 Feb 2004:
    Fix rarpboot: add autoload by NFS

    * Patch by Dan Eisenhut, 26 Feb 2004:
    fix flash_write return value in saveenv

    * Patch by Stephan Linz, 11 Dec 2003
    expand config.mk to avoid trigraph warnings on NIOS

    * Rename "BMS2003" board into "HMI10"

    wdenk
     

28 Jun, 2003

1 commit

  • - 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
     

06 Mar, 2003

3 commits

  • Cleanup compiler warning

    wdenk
     
  • - fix bug in BOOTP code (must use NetCopyIP)
    - update of CSB226 port
    - clear BSS segment on XScale
    - added support for i2c_init_board() function
    - update to the Innokom plattform

    * Extend support for redundand environments for configurations where
    environment size < sector size

    wdenk
     
  • - Add support for Innokom board
    - Don't complain if "install" fails
    - README cleanup (remove duplicated lines)
    - Update PXA header files

    * Add documentation for existing POST code (doc/README.POST)

    * Patch by Laudney Ren, 15 Jan 2003:
    Fix handling of redundand environment in "tools/envcrc.c"

    * Patch by Detlev Zundel, 28 Feb 2003:
    Add bedbug support for 824x systems

    * Add support for 16 MB flash configuration of TRAB board

    * Patch by Erwin Rol, 27 Feb 2003:
    Add support for RTEMS

    * Add image information to README

    * Fix dual PCMCIA slot support (when running with just one
    slot populated)

    * Add VFD type detection to trab board

    * extend drivers/cs8900.c driver to synchronize ethaddr environment
    variable with value in the EEPROM

    wdenk
     

03 Nov, 2002

1 commit