1. 13 Oct, 2010 24 commits
  2. 12 Oct, 2010 16 commits
    • Brent Darley's avatar
      TSI148: Fix argument parsing · 076f1be8
      Brent Darley authored
      
      
      This patch does 2 things:
       - Fix the argument number assigned to the vdw (VME data width) value.
         Previously, a nonexistent 7th arument was read as the vdw variable.
      
       - Reduce the size of the argument array for the tsi148 command from
         8 to 7.  The tsi148 command itself is argument index 0, and the
         maximum number arguments passed to the command is 6, making a total
         of 7 for the array.
      Signed-off-by: default avatarBrent Darley <bdarley@xes-inc.com>
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      076f1be8
    • Peter Tyser's avatar
      powerpc: Remove warm reset entry point · 52ebd9c1
      Peter Tyser authored
      
      
      No boards utilize the warm reset entry point, so remove it.
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      52ebd9c1
    • Peter Tyser's avatar
      ppmc7xx: Use _start as reset entry point · 3792d743
      Peter Tyser authored
      
      
      Previously the _warm_start label was used as an entry point.  These 2
      entry points should be functionally identical after the removal of the
      BOOTFLAG_WARM define.
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      3792d743
    • Peter Tyser's avatar
      powerpc: Zero out board info struct on bootup · a1c4864a
      Peter Tyser authored
      
      
      This puts the board info struct in a known state and allows the removal
      of other code which initialized board info fields to 0.
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      a1c4864a
    • Stefan Roese's avatar
      cp/cmp: Add WATCHDOG_RESET in copy and compare loop · eaadb44e
      Stefan Roese authored
      
      
      On some boards with a very short watchdog timeout, the "cp" and
      "cmp" commands may reset the board. This patch adds some
      watchdog resets inside the loops. Otherwise for example the lwmon5
      board will reset while doing something like this:
      
      => cp.b fc000000 1000000 100000
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      eaadb44e
    • Peter Tyser's avatar
      examples/standalone: Use gcc's -fno-toplevel-reorder · c91d456c
      Peter Tyser authored
      Using -fno-toplevel-reorder causes gcc to not reorder functions.  This
      ensures that an application's entry point will be the first function in
      the application's source file.
      
      This change, along with commit 620bbba5
      
      
      should cause a standalone application's entry point to be at the base of
      the compiled binary.  Previously, the entry point could change depending
      on gcc version and flags.
      
      Note -fno-toplevel-reorder is only available in gcc version 4.2 or
      greater.
      Signed-off-by: default avatarPeter Tyser <ptyser@xes-inc.com>
      c91d456c
    • Ilya Yanok's avatar
      a4m072: support for SHOW_BOOT_PROGRESS feature using LED display · 92d1a400
      Ilya Yanok authored
      
      
      This patch adds support for displaying boot progress codes on a4m072 board
      using LED display. As we can display only one symbol at any time on the hardware
      (two symbols with blinking) we can't display progress codes directly and have
      to map them to 2-symbol codes.
      We use the following mapping on the a4m972 board:
       [1, 8] U [100, 108]					-> 5
       [-9, -1] U [-101, -100] U [-113, -103]			-> -5
       [9, 14] U [120, 123] U [125, 129]			-> 8
       [-13, -10] U [-122, -120] U [-127, -124] U {-129}	-> -8
       {15}							-> 9
       [-32, -30]						-> -A
       [-40, -35] U [-51, -42] U [-58, -53] U
      		[-83, -80] U {-64, -130, -140, -150}	-> -B
      
      Other progress code are ignored. One symbol codes are displayed steady while
      two-symbol codes are displayed using blinking. Boot progress codes are
      displayed with decimal got unset (as opposed to 'display' command output).
      Signed-off-by: default avatarIlya Yanok <yanok@emcraft.com>
      92d1a400
    • Ilya Yanok's avatar
      a4m072: led display support · cb5639cb
      Ilya Yanok authored
      
      
      This patch adds support for LED display on a4m072 board. Hardware is
      capable of displaying only one symbol at any time. We support displaying
      two symbols in software (via blinking).
      Signed-off-by: default avatarIlya Yanok <yanok@emcraft.com>
      cb5639cb
    • Ilya Yanok's avatar
      led_display: split led display support into generic and hw-dependent parts · 7f0d241d
      Ilya Yanok authored
      
      
      Split the display command into generic interface and hardware-specific
      realization for PDSP188x LED display found on hmi1001 and manroland
      boards. Simple interface for LED displays is defined in
      include/led-display.h and described in doc/README.LED_display.
      Driver-specific implementation was moved into drivers/misc/pdsp188x.c
      file (enabled with CONFIG_PDSP188x set).
      Signed-off-by: default avatarIlya Yanok <yanok@emcraft.com>
      7f0d241d
    • Sergei Poselenov's avatar
      A4M072: Added support for the board. · 9531a238
      Sergei Poselenov authored
      
      
      This patch provides support for the A4M072 board with the following features:
       UART
       NOR flash
       FEC Ethernet
       External SRAM
       I2C EEPROM
       CompactFlash cards on IDE/ATA port
       USB Host
       PCI initialization
      
      The 7-segment LED indicator is not yet supported.
      Signed-off-by: default avatarSergei Poselenov <sposelenov@emcraft.com>
      9531a238
    • Mikhail Zolotaryov's avatar
      VFAT: fix processing of scattered long file name entries · 3831530d
      Mikhail Zolotaryov authored
      
      
      The U-Boot code has the following bugs related to the processing of Long File
      Name (LFN) entries scattered across several clusters/sectors :
      
      1) get_vfatname() function is designed to gather scattered LFN entries by
      cluster chain processing - that doesn't work for FAT12/16 root directory.
      In other words, the function expects the following input data:
       1.1) FAT32 directory (which is cluster chain based);
              OR
       1.2) FAT12/16 non-root directory (which is also cluster chain based);
              OR
       1.3) FAT12/16 root directory (allocated as contiguous sectors area), but
       all necessary information MUST be within the input buffer of filesystem cluster
       size (thus cluster-chain jump is never initiated).
      
      In order to accomplish the last condition, root directory parsing code in
      do_fat_read() uses the following trick: read-out cluster-size block, process
      only first sector (512 bytes), then shift 512 forward, read-out cluster-size
      block and so on. This works great unless cluster size is equal to 512 bytes
      (in a case you have a small partition), or long file name entries are scattered
      across three sectors, see 4) for details.
      
      2) Despite of the fact that get_vfatname() supports FAT32 root directory
      browsing, do_fat_read() function doesn't send current cluster number correctly,
      so root directory look-up doesn't work correctly.
      
      3) get_vfatname() doesn't gather scattered entries correctly also is the case
      when all LFN entries are located at the end of the source cluster, but real
      directory entry (which must be returned) is at the only beginning of the
      next one. No error detected, the resulting directory entry returned contains
      a semi-random information (wrong size, wrong start cluster number and so on)
      i.e. the entry is not accessible.
      
      4) LFN (VFAT) allows up to 20 entries (slots) each containing 26 bytes (13
      UTF-16 code units) to represent a single long file name i.e. up to 520 bytes.
      U-Boot allocates 256 bytes buffer instead, i.e. 10 or more LFN slots record
      may cause buffer overflow / memory corruption.
      Also, it's worth to mention that 20+1 slots occupy 672 bytes space which may
      take more than one cluster of 512 bytes (medium-size FAT32 or small FAT16
      partition) - get_vfatname() function doesn't support such case as well.
      
      The patch attached fixes these problems in the following way:
      - keep using 256 bytes buffer for a long file name, but safely prevent a
      possible buffer overflow (skip LFN processing, if it contains 10 or more
      slots).
      
      - explicitly specify FAT12/16 root directory parsing buffer size, instead
      of relying on cluster size. The value used is a double sector size (to store
      current sector and the next one). This fixes the first problem and increases
      performance on big FAT12/16 partitions;
      
      - send current cluster number (FAT32) to get_vfatname() during root
      directory processing;
      
      - use LFN counter to seek the real directory entry in get_vfatname() - fixes the
      third problem;
      
      - skip deleted entries in the root directory (to prevent bogus buffer
      overflow detection and LFN counter steps).
      
      Note: it's not advised to split up the patch, because a separate part may
      operate incorrectly.
      Signed-off-by: default avatarMikhail Zolotaryov <lebon@lebon.org.ua>
      3831530d
    • Daniel Hobi's avatar
      tools/imls: fix comment in Makefile · b75a2dde
      Daniel Hobi authored
      Commit d984fed0
      
       (makefiles: fixes for building build tools)
      changed the variable name FIT_CFLAGS to HOSTCFLAGS_NOPED
      but forgot to update to corresponding comment.
      Signed-off-by: default avatarDaniel Hobi <daniel.hobi@schmid-telecom.ch>
      Cc: Scott Wood <scottwood@freescale.com>
      Cc: Wolfgang Denk <wd@denx.de>
      b75a2dde
    • Lei Wen's avatar
      env: don't set to default env twice when use CONFIG_ENV_IS_NOWHERE · d259079d
      Lei Wen authored
      
      
      When use the CONFIG_ENV_IS_NOWHERE, I met such issue:
      
      	DRAM:  256 MiB
      	Using default environment
      
      	*** Warning - bad CRC, using default environment
      Signed-off-by: default avatarLei Wen <leiwen@marvell.com>
      d259079d
    • Stefan Roese's avatar
      zlib: Add further watchdog reset calls · be4424c7
      Stefan Roese authored
      Patch 253cb831
      
       [zlib: add watchdog reset call] added already a few
      watchdog reset calls to the new zlib U-Boot port. But on some boards
      this is not enough. Additional calls are needed on boards with
      short watchdog timeouts.
      
      This was detected and tested on the lwmon5 board with a very short
      watchdog timeout. Without this patch, the board resets during Linux
      kernel decompression. With it, the decompression succeeds.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Detlev Zundel <dzu@denx.de>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      be4424c7
    • Stefan Roese's avatar
      zlib/gunzip: Use WATCHDOG_RESET macro · f8526286
      Stefan Roese authored
      
      
      As usually done in U-Boot, the watchdog_reset code is called via a
      macro (WATCHDOG_RESET). In zlib.c this was done differently, by using
      a function pointer which is initialized with WATCHDOG_RESET upon watchdog
      usage or with NULL otherwise. This patch now uses the plain
      WATCHDOG_RESET macros to call the function resulting in slightly smaller
      U-Boot images and simpler code.
      
      U-Boot code size reduction:
      
      PowerPC board with watchdog support (lwmon5):
      -> 80 bytes smaller image size
      
      PowerPC board without watchdog support (sequoia):
      -> 112 bytes smaller image size
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      Cc: Detlev Zundel <dzu@denx.de>
      Cc: Wolfgang Denk <wd@denx.de>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      f8526286
    • Anatolij Gustschin's avatar
      pdm360ng: add EDID property to FDT display node · 6213b8ff
      Anatolij Gustschin authored
      
      
      PDM360NG board uses this functionality to pass display
      timing info to the Linux Framebuffer driver.
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      6213b8ff