15 Oct, 2013

1 commit


21 Aug, 2013

1 commit


24 Jul, 2013

1 commit


14 Dec, 2012

5 commits

  • Add support for read-only, write-once, and change-default.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     
  • Currently just validates variable types as decimal, hexidecimal,
    boolean, ip address, and mac address.

    If the entry is not found in the env ".flags", then look in the static
    one. This allows the env to override the static definitions, but prevents
    the need to have every definition in the environment distracting you.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     
  • Move the getenv_yesno() to env_common.c and change most checks for
    'y' or 'n' to use this helper.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     
  • Move the read of the old value to inside the check function. In some
    cases it can be avoided all together and at the least the code is only
    called from one place.

    Also name the function and the callback to more clearly describe what
    it does.

    Pass the ENTRY instead of just the name for direct access to the whole
    data structure.

    Pass an enum to the callback that specifies the operation being approved.

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     
  • Use a flag in hsearch_r for insert mode passed from import to allow the
    behavior be different based on use.

    Now that "do_check" is called for all imports, ensure console init is
    complete before updating the console on relocation import

    Signed-off-by: Joe Hershberger

    Joe Hershberger
     

20 Oct, 2012

1 commit


16 Oct, 2012

1 commit


02 Oct, 2012

1 commit

  • This patch adds support for networking in SPL. Some devices are
    capable of loading SPL via network so it makes sense to load the
    main U-Boot binary via network too. This patch tries to use
    existing network code as much as possible. Unfortunately, it depends
    on environment which in turn depends on other code so SPL size
    is increased significantly. No effort was done to decouple network
    code and environment so far.

    Signed-off-by: Ilya Yanok
    Acked-by: Joe Hershberger
    Signed-off-by: Tom Rini

    Ilya Yanok
     

19 Sep, 2012

4 commits

  • 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
     
  • 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
     
  • Add 2 new arguments to himport_r():

    o "nvars", "vars": number and list of variables to take into account
    (0 means ALL)

    NOTE: This patch does not change the current behaviour.

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

    Gerlando Falauto
     
  • The ethprime env var was missing from env_common.

    Signed-off-by: Benoît Thébaudeau
    Cc: Wolfgang Denk

    Benoît Thébaudeau
     

10 Jul, 2012

1 commit

  • This can be useful for generic scripts. For example, rather than hard-
    coding a script to ext2load tegra-harmony.dtb, it could load
    ${soc}-${board}.dtb and hence not need adjustments to run on multiple
    boards.

    Signed-off-by: Stephen Warren
    Acked-by: Simon Glass
    Signed-off-by: Tom Warren

    Stephen Warren
     

19 Mar, 2012

3 commits


05 Jan, 2012

1 commit


22 Nov, 2011

1 commit


22 Oct, 2011

2 commits


26 Jul, 2011

1 commit


10 Jan, 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
     

30 Oct, 2010

1 commit

  • By now, the majority of architectures have working relocation
    support, so the few remaining architectures have become exceptions.
    To make this more obvious, we make working relocation now the default
    case, and flag the remaining cases with CONFIG_NEEDS_MANUAL_RELOC.

    Signed-off-by: Wolfgang Denk
    Tested-by: Heiko Schocher
    Tested-by: Reinhard Meyer

    Wolfgang Denk
     

13 Oct, 2010

1 commit


07 Oct, 2010

1 commit

  • commit ea882baf9c17cd142c99e3ff640d3ab01daa5cec introduces
    a command_sub_table for the "env" command. On arm, avr32, m68k,
    mips and sparc architectures, relocation needs manual fixups,
    so add these fixups for this sub command table too.

    Tested on arm/qong board.
    mips board (Ben NanoNote) from Xiangfu Liu
    arm/AT91 board from Reinhard Meyer

    Signed-off-by: Heiko Schocher

    cc: Wolfgang Denk
    cc: Shinya Kuribayashi
    cc: Xiangfu Liu
    cc: Reinhard Meyer
    cc: sshtylyov@mvista.com

    Heiko Schocher
     

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
     

18 Jul, 2010

1 commit

  • The board maintainer states:

    The GTH board is obsolete and has not been manufactured for
    several years.
    To my knowledge, no recent U-Boot build has been tested on that
    card.

    So drop support for this board.

    Signed-off-by: Wolfgang Denk
    Cc: Thomas Lange
    Acked-by: Thomas Lange

    Wolfgang Denk
     

24 Jun, 2010

1 commit

  • The AmigaOneG3SE board has been orphaned or a very long time, and
    broken for more than 12 releases resp. more than 3 years. As nobody
    seems to be interested any more in this stuff we may as well ged rid
    of it, especially as it clutters many areas of the code so it is a
    continuous pain for all kinds of ongoing work.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

03 Oct, 2009

1 commit

  • Add #ifdefs where necessary to not perform relocation fixups. This
    allows boards/architectures which support relocation to trim a decent
    chunk of code.

    Note that this patch doesn't add #ifdefs to architecture-specific code
    which does not support relocation.

    Signed-off-by: Peter Tyser

    Peter Tyser
     

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
     

19 Oct, 2008

2 commits


11 Sep, 2008

4 commits