1. 29 Oct, 2010 1 commit
  2. 27 Oct, 2010 1 commit
  3. 26 Oct, 2010 1 commit
    • Wolfgang Denk's avatar
      Rename CONFIG_SYS_INIT_RAM_END into CONFIG_SYS_INIT_RAM_SIZE · 553f0982
      Wolfgang Denk authored
      
      
      CONFIG_SYS_INIT_RAM_END was a misnomer as it suggests this might be
      some end address; to make the meaning more clear we rename it into
      CONFIG_SYS_INIT_RAM_SIZE
      
      No other code changes are performed in this patch, only minor editing
      of white space (due to the changed length) and the comments was done,
      where noticed.
      
      Note that the code for the PATI and cmi_mpc5xx board configurations
      looks seriously broken.  Last known maintainers on Cc:
      Signed-off-by: Wolfgang Denk's avatarWolfgang Denk <wd@denx.de>
      Cc: Denis Peter <d.peter@mpl.ch>
      Cc: Martin Winistoerfer <martinwinistoerfer@gmx.ch>
      Acked-by: default avatarKumar Gala <galak@kernel.crashing.org>
      553f0982
  4. 18 Oct, 2010 2 commits
    • John Rigby's avatar
      boot: change some arch ifdefs to feature ifdefs · fca43cc8
      John Rigby authored and Wolfgang Denk's avatar Wolfgang Denk committed
      
      
      The routines boot_ramdisk_high, boot_get_cmdline and boot_get_kbd
      are currently enabled by various combinations of CONFIG_M68K,
      CONFIG_POWERPC and CONFIG_SPARC.
      
      Use CONFIG_SYS_BOOT_<FEATURE> defines instead.
      
      CONFIG_SYS_BOOT_RAMDISK_HIGH
      CONFIG_SYS_BOOT_GET_CMDLINE
      CONFIG_SYS_BOOT_GET_KBD
      
      Define these as appropriate in arch/include/asm/config.h files.
      Signed-off-by: default avatarJohn Rigby <john.rigby@linaro.org>
      Acked-by: Wolfgang Denk's avatarWolfgang Denk <wd@denx.de>
      fca43cc8
    • Wolfgang Denk's avatar
      Rename TEXT_BASE into CONFIG_SYS_TEXT_BASE · 14d0a02a
      Wolfgang Denk authored
      
      
      The change is currently needed to be able to remove the board
      configuration scripting from the top level Makefile and replace it by
      a simple, table driven script.
      
      Moving this configuration setting into the "CONFIG_*" name space is
      also desirable because it is needed if we ever should move forward to
      a Kconfig driven configuration system.
      Signed-off-by: Wolfgang Denk's avatarWolfgang Denk <wd@denx.de>
      14d0a02a
  5. 11 Oct, 2010 1 commit
  6. 06 Oct, 2010 1 commit
  7. 28 Sep, 2010 1 commit
  8. 23 Sep, 2010 2 commits
  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: Wolfgang Denk's 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. 09 Aug, 2010 1 commit
    • Heiko Schocher's avatar
      net ppc: fix ethernet device names with spaces · 48690d80
      Heiko Schocher authored
      since commit 1384f3bb
      
       ethernet names
      with spaces drop a
      
      Warning: eth device name has a space!
      
      message. This patch fix it for:
      
      - "FEC ETHERNET" devices found on
        mpc512x, mpc5xxx, mpc8xx and mpc8220 boards.
        renamed to "FEC".
      - "SCC ETHERNET" devices found on
        mpc8xx, mpc82xx based boards. Renamed to "SCC".
      - "HDLC ETHERNET" devices found on mpc8xx boards
        Renamed to "HDLC"
      - "FCC ETHERNET" devices found on mpc8260 and mpc85xx based
        boards. Renamed to "FCC"
      
      Tested on the kup4k board.
      Signed-off-by: Heiko Schocher's avatarHeiko Schocher <hs@denx.de>
      Signed-off-by: default avatarBen Warren <biggerbadderben@gmail.com>
      48690d80
  11. 03 Aug, 2010 1 commit
    • Wolfgang Denk's avatar
      Rename getenv_r() into getenv_f() · cdb74977
      Wolfgang Denk authored
      
      
      While running from flash, i. e. before relocation, we have only a
      limited C runtime environment without writable data segment. In this
      phase, some configurations (for example with environment in EEPROM)
      must not use the normal getenv(), but a special function.  This
      function had been called getenv_r(), with the idea that the "_r"
      suffix would mean the same as in the _r_eentrant versions of some of
      the C library functions (for example getdate vs. getdate_r, getgrent
      vs. getgrent_r, etc.).
      
      Unfortunately this was a misleading name, as in U-Boot the "_r"
      generally means "running from RAM", i. e. _after_ relocation.
      
      To avoid confusion, rename into getenv_f() [as "running from flash"]
      Signed-off-by: Wolfgang Denk's avatarWolfgang Denk <wd@denx.de>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      cdb74977
  12. 22 Jul, 2010 1 commit
  13. 13 Jun, 2010 1 commit
  14. 28 May, 2010 2 commits
  15. 03 May, 2010 1 commit
  16. 21 Apr, 2010 1 commit
  17. 19 Apr, 2010 1 commit
    • Richard Retanubun's avatar
      fsl_i2c: Added a callpoint for i2c_board_late_init · 26a33504
      Richard Retanubun authored and Heiko Schocher's avatar Heiko Schocher committed
      This patch adds a callpoint in i2c_init that allows board specific
      i2c board initialization (typically for i2c bus reset) that is called
      after i2c_init operations, allowing the i2c_board_late_init function
      to use the pre-configured i2c bus speed and slave address.
      26a33504
  18. 13 Apr, 2010 4 commits
  19. 08 Apr, 2010 1 commit
  20. 21 Mar, 2010 1 commit
  21. 01 Feb, 2010 1 commit
  22. 26 Jan, 2010 1 commit
  23. 17 Jan, 2010 1 commit
    • Heiko Schocher's avatar
      cmd_eeprom: I2C updates · 548738b4
      Heiko Schocher authored and Wolfgang Denk's avatar Wolfgang Denk committed
      
      
      - CONFIG_ENV_EEPROM_IS_ON_I2C
        define this, if you have I2C and SPI activated, and your
        EEPROM, which holds the environment, is on the I2C bus.
      
      - CONFIG_I2C_ENV_EEPROM_BUS
        if you have an Environment on an EEPROM reached over
        I2C muxes, you can now define, how to reach this
        EEPROM.
      Signed-off-by: Heiko Schocher's avatarHeiko Schocher <hs@denx.de>
      548738b4
  24. 08 Dec, 2009 1 commit
  25. 07 Dec, 2009 1 commit
  26. 05 Dec, 2009 1 commit
  27. 02 Dec, 2009 1 commit
  28. 27 Oct, 2009 2 commits
  29. 18 Oct, 2009 1 commit
    • Mike Frysinger's avatar
      env: only build env_embedded and envcrc when needed · 6dab6add
      Mike Frysinger authored and Wolfgang Denk's avatar Wolfgang Denk committed
      
      
      The env code is protected by the ENV_IS_EMBEDDED define, so attempting to
      compile the code when this isn't defined is pointless.  Now that the env
      headers have unified around CONFIG_ENV_IS_EMBEDDED, convert the build
      system to only build the env objects when this is enabled.  And now that
      the env code is conditionally compiled, we can drop the source code checks.
      
      For people who want to extract the environment manually, add a new option
      CONFIG_BUILD_ENVCRC that only enables the envcrc utility.
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      6dab6add
  30. 03 Oct, 2009 4 commits