1. 06 Dec, 2011 1 commit
  2. 22 Nov, 2011 3 commits
  3. 08 Nov, 2011 1 commit
    • Wolfgang Denk's avatar
      env: allow to export only selected variables · 37f2fe74
      Wolfgang Denk authored
      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: default avatarWolfgang Denk <wd@denx.de>
      37f2fe74
  4. 24 May, 2011 1 commit
  5. 08 Feb, 2011 1 commit
  6. 02 Feb, 2011 1 commit
  7. 17 Dec, 2010 1 commit
    • Mike Frysinger's avatar
      hashtable: drop all non-reentrant versions · 2eb1573f
      Mike Frysinger authored
      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: default avatarMike Frysinger <vapier@gentoo.org>
      2eb1573f
  8. 07 Dec, 2010 1 commit
  9. 19 Sep, 2010 1 commit
    • Wolfgang Denk's avatar
      New implementation for internal handling of environment variables. · ea882baf
      Wolfgang Denk authored
      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 <matthias.fuchs@esd-electronics.com>,
      	       Stefan Roese <sr@denx.de>,
      	       Heiko Schocher <hs@denx.de>
      
      - Dropping forceenv() causes build problems on schmoogie
      
      	=> cc: Sergey Kubushyn <ksi@koi8.net>
      
      - Build tested on PPC and ARM only; runtime tested with NOR and NAND
        flash only => needs testing!!
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Cc: Matthias Fuchs <matthias.fuchs@esd-electronics.com>,
      Cc: Stefan Roese <sr@denx.de>,
      Cc: Heiko Schocher <hs@denx.de>
      Cc: Sergey Kubushyn <ksi@koi8.net>
      ea882baf
  10. 13 Aug, 2010 1 commit
  11. 12 Jul, 2010 2 commits
    • Scott Wood's avatar
      NAND: formatting cleanups from env.oob support · 53504a27
      Scott Wood authored
      Change if (ok) {
      	bunch of stuff
      } else {
      	error
      }
      
      to
      
      if (error) {
      	get out
      }
      
      proceed with bunch of stuff
      
      Plus a few whitespace cleanups.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      53504a27
    • Ben Gardiner's avatar
      NAND: environment offset in OOB (CONFIG_ENV_OFFSET_OOB) · c9f7351b
      Ben Gardiner authored
      This is a re-submission of the patch by Harald Welte
      <laforge@openmoko.org> with minor modifications for rebase and changes
      as suggested by Scott Wood <scottwood@freescale.com> [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/79195Signed-off-by: default avatarBen Gardiner <bengardiner@nanometrics.ca>
      Acked-by: default avatarHarald Welte <laforge@gnumonks.org>
      c9f7351b
  12. 04 Jul, 2010 1 commit
  13. 27 Jan, 2010 1 commit
  14. 09 Aug, 2009 1 commit
  15. 17 Jul, 2009 1 commit
    • Scott Wood's avatar
      Remove legacy NAND and disk on chip code. · be33b046
      Scott Wood authored
      Legacy NAND had been scheduled for removal.  Any boards that use this
      were already not building in the previous release due to an #error.
      
      The disk on chip code in common/cmd_doc.c relies on legacy NAND,
      and it has also been removed.  There is newer disk on chip code
      in drivers/mtd/nand; someone with access to hardware and sufficient
      time and motivation can try to get that working, but for now disk
      on chip is not supported.
      Signed-off-by: default avatarScott Wood <scottwood@freescale.com>
      be33b046
  16. 07 Jul, 2009 2 commits
  17. 17 Feb, 2009 1 commit
  18. 06 Feb, 2009 1 commit
  19. 10 Sep, 2008 3 commits
  20. 12 Aug, 2008 1 commit
  21. 09 Jul, 2008 2 commits
  22. 28 Jun, 2008 1 commit
  23. 16 Jun, 2008 1 commit
  24. 06 Jun, 2008 1 commit
  25. 28 May, 2008 1 commit
  26. 20 May, 2008 1 commit
    • Wolfgang Denk's avatar
      Big white-space cleanup. · 53677ef1
      Wolfgang Denk authored
      This commit gets rid of a huge amount of silly white-space issues.
      Especially, all sequences of SPACEs followed by TAB characters get
      removed (unless they appear in print statements).
      
      Also remove all embedded "vim:" and "vi:" statements which hide
      indentation problems.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      53677ef1
  27. 13 May, 2008 1 commit
  28. 30 Apr, 2008 1 commit
  29. 29 Apr, 2008 1 commit
  30. 28 Apr, 2008 1 commit
  31. 09 Jan, 2008 1 commit
  32. 10 Jul, 2007 1 commit
  33. 08 Jul, 2007 1 commit