1. 06 Aug, 2012 1 commit
  2. 30 Apr, 2012 1 commit
  3. 05 Jan, 2012 1 commit
  4. 22 Nov, 2011 3 commits
  5. 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>
  6. 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>
  7. 19 Sep, 2010 1 commit
    • Wolfgang Denk's avatar
      New implementation for internal handling of environment variables. · ea882baf
      Wolfgang Denk authored
      * 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.
      - "printenv" will '\\'-escape the '\n' in multi-line variables, while
        "printenv var" will not do that.
      - "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")
      - Image size grows by typically 5...7 KiB (might shrink a bit again on
        systems with redundant environment with a following patch series)
      - 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'
              Usage szenario: create a text snapshot/backup of the current
      		=> 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
      - 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>
  8. 06 Jan, 2010 1 commit
    • Sanjeev Premi's avatar
      onenand: Fix compile errors due to FlexOneNAND · b821cead
      Sanjeev Premi authored
      This patch fixes the compile error while trying to
      compile for omap3evm.
      env_onenand.c: In function 'env_relocate_spec':
      env_onenand.c:70: error: 'CONFIG_ENV_ADDR_FLEX' undeclared
       (first use in this function)
      env_onenand.c:70: error: (Each undeclared identifier is re
      ported only once
      env_onenand.c:70: error: for each function it appears in.)
      env_onenand.c: In function 'saveenv':
      env_onenand.c:106: error: 'CONFIG_ENV_ADDR_FLEX' undeclare
      d (first use in this function)
      env_onenand.c:107: error: 'CONFIG_ENV_SIZE_FLEX' undeclare
      d (first use in this function)
      Signed-off-by: default avatarSanjeev Premi <premi@ti.com>
      Acked-by: default avatarTom Rix <Tom.Rix@windriver.com>
  9. 13 Nov, 2009 1 commit
  10. 26 Jul, 2009 1 commit
  11. 16 Jul, 2009 1 commit
  12. 07 Jul, 2009 1 commit
  13. 12 Jun, 2009 1 commit
    • Stefan Roese's avatar
      mtd: Update MTD infrastructure to support 64bit device size · 8d2effea
      Stefan Roese authored
      This patch brings the U-Boot MTD infrastructure in sync with the current
      Linux MTD version (2.6.30-rc3). Biggest change is the 64bit device size
      support and a resync of the mtdpart.c file which has seen multiple fixes
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Scott Wood <scottwood@freescale.com>
      Cc: Kyungmin Park <kmpark@infradead.org>
  14. 02 Dec, 2008 1 commit
  15. 10 Sep, 2008 3 commits
  16. 13 Aug, 2008 1 commit
  17. 10 Aug, 2008 1 commit
    • dirk.behme@googlemail.com's avatar
      OneNAND: Remove base address offset usage · aa5ffa16
      dirk.behme@googlemail.com authored
      While locally preparing some U-Boot patches for ARM based OMAP3 boards, some
      using OneNAND and some using NAND, we found some differences in OneNAND and
      NAND command address handling.
      As this might confuse users (it already confused us), we like to align OneNAND
      and NAND address handling.
      The issue is that cmd_onenand.c subtracts the onenand base address from the
      addresses you type into the u-boot command line so, unlike nand, you can't
      use addresses relative to the start of the onenand part e.g. this won't work:
      onenand read 82000000 280000 400000
      you have to use:
      onenand read 82000000 20280000 400000
      Looking at recent git, the only board currently using OneNAND is Apollon, and
      for this the OneNAND base address is 0 (apollon.h)
      #define	CFG_ONENAND_BASE	0x00000000
      so patch below won't break any existing boards and will align OneNAND and NAND
      handling on boards where OneNAND base address is != 0.
      Signed-off-by: default avatarSteve Sakoman <sakoman@gmail.com>
      Signed-off-by: default avatarManikandan Pillai <mani.pillai@ti.com>
      Signed-off-by: default avatarDirk Behme <dirk.behme@gmail.com>
  18. 13 Jul, 2008 1 commit
  19. 14 Apr, 2008 1 commit
  20. 15 Nov, 2007 1 commit
  21. 17 Sep, 2007 1 commit