1. 10 Oct, 2011 1 commit
    • Xiangfu Liu's avatar
      MIPS: Ingenic XBurst Jz4740 processor support · 80421fcc
      Xiangfu Liu authored
      Jz4740 is a multimedia application processor targeting for mobile
      devices like e-Dictionary, eBook, portable media player (PMP) and
      GPS navigator.  Jz4740 is powered by Ingenic 360 MHz XBurst CPU core
      (JzRISC), in which RISC/SIMD/DSP hybrid instruction set architecture
      provides high integration, high performance and low power consumption.
      
      JzRISC incorporated in Jz4740 is the advanced and power-efficient
      32-bit RISC core, compatible with MIPS32, with 16K I-Cache and 16K
      D-Cache, and can operate at speeds up to 400 MHz.
      
      On-chip modules such as LCD controller, embedded audio codec, multi-
      channel SAR-ADC, AC97/I2S controller and camera I/F offer a rich
      suite of peripherals for multimedia application.  NAND controller
      (SLC/MLC), USB (host 1.1 and device 2.0), UART, I2C, SPI, etc. are
      also available.
      
      For more info about Ingenic XBurst Jz4740:
        http://en.ingenic.cn/eng/
        http://www.linux-mips.org/wiki/Ingenic
      
      
      
      This patch introduces XBurst CPU support in U-Boot.  It's compatible
      with MIPS32, but requires a bit different cache maintenance, timer
      routines, and boot mechanism using USB boot tool, so XBurst support
      can go into a separate new home, cpu/xburst/.
      Signed-off-by: default avatarXiangfu Liu <xiangfu@openmobilefree.net>
      Acked-by: default avatarDaniel <zpxu@ingenic.cn>
      Signed-off-by: default avatarShinya Kuribayashi <skuribay@pobox.com>
      80421fcc
  2. 05 Oct, 2011 3 commits
  3. 03 Sep, 2011 1 commit
  4. 31 Jul, 2011 2 commits
  5. 28 Jul, 2011 1 commit
  6. 26 Jul, 2011 2 commits
  7. 09 May, 2011 2 commits
  8. 06 May, 2011 2 commits
  9. 12 Apr, 2011 1 commit
    • Wolfgang Denk's avatar
      Make STANDALONE_LOAD_ADDR configurable per board · 8ae86b76
      Wolfgang Denk authored
      
      
      Rename STANDALONE_LOAD_ADDR into CONFIG_STANDALONE_LOAD_ADDR
      and allow that the architecture-specific default value gets
      overwritten by defining the value in the board header file.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Cc: Mike Frysinger <vapier@gentoo.org>
      Cc: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
      Cc: Daniel Hellstrom <daniel@gaisler.com>
      Cc: Tsi Chung Liew <tsi-chung.liew@freescale.com>
      Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
      8ae86b76
  10. 02 Apr, 2011 5 commits
  11. 17 Nov, 2010 1 commit
    • Sebastien Carlier's avatar
      Switch from archive libraries to partial linking · 6d8962e8
      Sebastien Carlier authored
      
      
      Before this commit, weak symbols were not overridden by non-weak symbols
      found in archive libraries when linking with recent versions of
      binutils.  As stated in the System V ABI, "the link editor does not
      extract archive members to resolve undefined weak symbols".
      
      This commit changes all Makefiles to use partial linking (ld -r) instead
      of creating library archives, which forces all symbols to participate in
      linking, allowing non-weak symbols to override weak symbols as intended.
      This approach is also used by Linux, from which the gmake function
      cmd_link_o_target (defined in config.mk and used in all Makefiles) is
      inspired.
      
      The name of each former library archive is preserved except for
      extensions which change from ".a" to ".o".  This commit updates
      references accordingly where needed, in particular in some linker
      scripts.
      
      This commit reveals board configurations that exclude some features but
      include source files that depend these disabled features in the build,
      resulting in undefined symbols.  Known such cases include:
      - disabling CMD_NET but not CMD_NFS;
      - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.
      Signed-off-by: default avatarSebastien Carlier <sebastien.carlier@gmail.com>
      6d8962e8
  12. 29 Oct, 2010 1 commit
  13. 26 Oct, 2010 1 commit
    • Wolfgang Denk's avatar
      Replace CONFIG_SYS_GBL_DATA_SIZE by auto-generated value · 25ddd1fb
      Wolfgang Denk authored
      
      
      CONFIG_SYS_GBL_DATA_SIZE has always been just a bad workarond for not
      being able to use "sizeof(struct global_data)" in assembler files.
      Recent experience has shown that manual synchronization is not
      reliable enough.  This patch renames CONFIG_SYS_GBL_DATA_SIZE into
      GENERATED_GBL_DATA_SIZE which gets automatically generated by the
      asm-offsets tool.  In the result, all definitions of this value can be
      deleted from the board config files.  We have to make sure that all
      files that reference such data include the new <asm-offsets.h> file.
      
      No other changes have been done yet, but it is obvious that similar
      changes / simplifications can be done for other, related macro
      definitions as well.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Acked-by: default avatarKumar Gala <galak@kernel.crashing.org>
      25ddd1fb
  14. 19 Oct, 2010 1 commit
  15. 19 Sep, 2010 5 commits
    • Heiko Schocher's avatar
      common: move TOTAL_MALLOC_LEN to include/common.h · 3fbeeea6
      Heiko Schocher authored
      
      
      Portions of this work were supported by funding from
      the CE Linux Forum.
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      3fbeeea6
    • Heiko Schocher's avatar
      relocation: fixup cmdtable · 620f1f6a
      Heiko Schocher authored
      
      
      fixup_cmdtable() did all work for fixing up the cmdtable,
      if CONFIG_RELOC_FIXUP_WORKS is not defined.
      
      CONFIG_RELOC_FIXUP_WORKS is missing for i386! I talked
      with Graeme Russ, and he will fix this soon.
      
      Portions of this work were supported by funding from
      the CE Linux Forum.
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      620f1f6a
    • Heiko Schocher's avatar
      arm: get rid of bi_env · 55e97429
      Heiko Schocher authored
      
      
      bi_env is nowhere used, so delete it!
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>
      
      similar patch posted from Dirk Behme Tue Jul 27 18:36:09 CEST 2010
      http://lists.denx.de/pipermail/u-boot/2010-July/074542.html
      55e97429
    • 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
    • Wolfgang Denk's avatar
      Make getenv() work before relocation. · 91a76751
      Wolfgang Denk authored
      
      
      So far, getenv() would work before relocation is most cases, even
      though it was not intended to be used that way.  When switching to a
      hash table based implementation, this would break a number of boards.
      
      For convenience, we make getenv() check if it's running before
      relocation and, if so, use getenv_f() internally.
      
      Note that this is limited to simple cases, as we use a small static
      buffer (32 bytes) in the global data for this purpose.
      
      For this reason, it is also not a good idea to convert all current
      uses of getenv_f() into getenv() - some of the existing use cases need
      to be able to deal with longer variable values, so getenv_f() is still
      needed and recommended for use before relocation.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      91a76751
  16. 09 Aug, 2010 1 commit
  17. 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: default avatarWolfgang Denk <wd@denx.de>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      cdb74977
  18. 04 Jul, 2010 1 commit
    • Wolfgang Denk's avatar
      Make sure that argv[] argument pointers are not modified. · 54841ab5
      Wolfgang Denk authored
      
      
      The hush shell dynamically allocates (and re-allocates) memory for the
      argument strings in the "char *argv[]" argument vector passed to
      commands.  Any code that modifies these pointers will cause serious
      corruption of the malloc data structures and crash U-Boot, so make
      sure the compiler can check that no such modifications are being done
      by changing the code into "char * const argv[]".
      
      This modification is the result of debugging a strange crash caused
      after adding a new command, which used the following argument
      processing code which has been working perfectly fine in all Unix
      systems since version 6 - but not so in U-Boot:
      
      int main (int argc, char **argv)
      {
      	while (--argc > 0 && **++argv == '-') {
      /* ====> */	while (*++*argv) {
      			switch (**argv) {
      			case 'd':
      				debug++;
      				break;
      			...
      			default:
      				usage ();
      			}
      		}
      	}
      	...
      }
      
      The line marked "====>" will corrupt the malloc data structures and
      usually cause U-Boot to crash when the next command gets executed by
      the shell.  With the modification, the compiler will prevent this with
      an
      	error: increment of read-only location '*argv'
      
      N.B.: The code above can be trivially rewritten like this:
      
      	while (--argc > 0 && **++argv == '-') {
      		char *arg = *argv;
      		while (*++arg) {
      			switch (*arg) {
      			...
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      Acked-by: default avatarMike Frysinger <vapier@gentoo.org>
      54841ab5
  19. 13 Apr, 2010 3 commits