Skip to content
Snippets Groups Projects
  1. Jan 21, 2010
  2. Jan 18, 2010
    • Daniel Hobi's avatar
      Makefile: fix parallel build · 2a998793
      Daniel Hobi authored
      
      During parallel build, the top Makefile spawns multiple sub-makes for
      targets in cpu/$(CPU) and $(dir $(LDSCRIPT)). If the .depend files are
      not present in these directories, the sub-makes may end up generating
      these files simultaneously which leads to corrupted content.
      
      A typical error message is:
      
      .depend:39: *** multiple target patterns.  Stop.
      
      This patch serializes the creation of .depend in cpu/$(CPU) and
      $(dir $(LDSCRIPT)) by adding these directories to the depend target
      in the top Makefile.
      
      Other directories in $(LIBS) are not affected since they contain only
      one Make target and thus only one sub-make is spawned per directory.
      
      Signed-off-by: default avatarDaniel Hobi <daniel.hobi@schmid-telecom.ch>
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      2a998793
  3. Jan 17, 2010
  4. Jan 08, 2010
    • Reinhard Arlt's avatar
      mpc83xx: Add support for MPC8349 esd caddy2 · 1dee9be6
      Reinhard Arlt authored
      
      The caddy2 is a variant of the already supported vme8349. So we just
      add the differences to this board port. To better support those two
      boards we switched from fixed SDRAM configuration to usage of
      spd_sdram(). This is done by providing a board specific SPD EEPROM
      routine with different values for both boards.
      
      Signed-off-by: default avatarReinhard Arlt <reinhard.arlt@esd.eu>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      
      changed to use mkconfig -t option instead, plus misc codingstyle fixes.
      
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      1dee9be6
    • Anton Vorontsov's avatar
      mpc83xx: Add NAND boot support for MPC8315E-RDB boards · 2e95004d
      Anton Vorontsov authored
      
      The core support for NAND booting is there already, so this patch
      is pretty straightforward.
      
      There is one trick though: top level Makefile expects nand_spl to
      be in nand_spl/board/$(BOARDDIR), but we can fully reuse the code
      from mpc8313erdb boards, and so to not duplicate the code we just
      symlink nand_spl/board/freescale/mpc8315erdb to mpc8313erdb.
      
      Signed-off-by: default avatarAnton Vorontsov <avorontsov@ru.mvista.com>
      
      o silence make during ln echo
      o update documentation
      o and avoid:
      
      $ ./MAKEALL MPC8315ERDB_NAND
      Configuring for MPC8315ERDB board...
      sdram.o: In function `fixed_sdram':
      /home/r1aaha/git/u-boot/nand_spl/board/freescale/mpc8313erdb/sdram.c:72: undefined reference to `udelay'
      
      by renaming udelay -> __udelay in the spirit of commit
      3eb90bad "Generic udelay() with watchdog
      support".
      
      Signed-off-by: default avatarKim Phillips <kim.phillips@freescale.com>
      2e95004d
  5. Dec 20, 2009
    • Tom Rix's avatar
      TWL4030 Add usb PHY support · bffbb2a8
      Tom Rix authored
      
      The twl4030 provides a PHY device for connecting a link device,
      like musb, to physical connection.
      
      This change adds the twl4030 usb registers and functions for
      initializing the PHY as required by omap3.
      
      Signed-off-by: default avatarTom Rix <Tom.Rix@windriver.com>
      bffbb2a8
  6. Dec 17, 2009
  7. Dec 15, 2009
  8. Dec 07, 2009
  9. Dec 05, 2009
  10. Nov 27, 2009
  11. Oct 31, 2009
  12. Oct 27, 2009
  13. Oct 24, 2009
    • Tom Rix's avatar
      TI OMAP3 SDP3430: Initial Support · e63e5904
      Tom Rix authored
      
      Start of support of
      Texas Instruments Software Development Platform(SDP)
      for OMAP3430 - SDP3430
      
      Highlights of this platform are:
      Flash Memory devices:
      	Sibley NOR, Micron 8bit NAND and OneNAND
      Connectivity:
      	3 UARTs and expanded 4 UART ports + IrDA
      	Ethernet, USB
      Other peripherals:
      	TWL5030 PMIC+Audio+Keypad
      	VGA display
      Expansion ports:
      	Memory devices plugin boards (PISMO)
      	Connectivity board for GPS,WLAN etc.
      Completely configurable boot sequence and device mapping
      etc.
      
      Support default jumpering and:
       - UART1/ttyS0 console(legacy sdp3430 u-boot)
       - UART3/ttyS2 console (matching other boards,
      		 and SDP HW docs)
       - Ethernet
       - mmc0
       - NOR boot
      
      Currently the UART1 is enabled by default.  for
      compatibility with other OMAP3 u-boot platforms,
      enable the #define of CONSOLE_J9.
      
      Conflicts:
      
      	Makefile
      
      Fixed the conflict with smdkc100_config by moving omap_sdp3430_config
      to it is alphabetically sorted location above zoom1.
      
      Signed-off-by: default avatarDavid Brownell <david-b@pacbell.net>
      Signed-off-by: default avatarNishanth Menon <nm@ti.com>
      Signed-off-by: default avatarTom Rix <Tom.Rix@windriver.com>
      e63e5904
  14. Oct 18, 2009
  15. Oct 16, 2009
  16. Oct 14, 2009
  17. Oct 13, 2009
  18. Sep 30, 2009
    • Mingkai Hu's avatar
      On-chip ROM boot: MPC8536DS support · e40ac487
      Mingkai Hu authored
      
      The MPC8536E is capable of booting from the on-chip ROM - boot from
      eSDHC and boot from eSPI. When power on, the porcessor excutes the
      ROM code to initialize the eSPI/eSDHC controller, and loads the mian
      U-Boot image from the memory device that interfaced to the controller,
      such as the SDCard or SPI EEPROM, to the target memory, e.g. SDRAM or
      L2SRAM, then boot from it.
      
      The memory device should contain a specific data structure with control
      word and config word at the fixed address. The config word direct the
      process how to config the memory device, and the control word direct
      the processor where to find the image on the memory device, or where
      copy the main image to. The user can use any method to store the data
      structure to the memory device, only if store it on the assigned address.
      
      The on-chip ROM code will map the whole 4GB address space by setting
      entry0 in the TLB1, so the main image need to switch to Address space 1
      to disable this mapping and map the address space again.
      
      This patch implements loading the mian U-Boot image into L2SRAM, so
      the image can configure the system memory by using SPD EEPROM.
      
      Signed-off-by: default avatarMingkai Hu <Mingkai.hu@freescale.com>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      e40ac487
    • Mingkai Hu's avatar
      NAND boot: MPC8536DS support · 9a1a0aed
      Mingkai Hu authored
      
      MPC8536E can support booting from NAND flash which uses the
      image u-boot-nand.bin. This image contains two parts: a 4K
      NAND loader and a main U-Boot image. The former is appended
      to the latter to produce u-boot-nand.bin. The 4K NAND loader
      includes the corresponding nand_spl directory, along with the
      code twisted by CONFIG_NAND_SPL. The main U-Boot image just
      like a general U-Boot image except the parts that included by
      CONFIG_SYS_RAMBOOT.
      
      When power on, eLBC will automatically load from bank 0 the
      4K NAND loader into the FCM buffer RAM where CPU can execute
      the boot code directly. In the first stage, the NAND loader
      copies itself to RAM or L2SRAM to free up the FCM buffer RAM,
      then loads the main image from NAND flash to RAM or L2SRAM
      and boot from it.
      
      This patch implements the NAND loader to load the main image
      into L2SRAM, so the main image can configure the RAM by using
      SPD EEPROM. In the first stage, the NAND loader copies itself
      to the second to last 4K address space, and uses the last 4K
      address space as the initial RAM for stack.
      
      Obviously, the size of L2SRAM shouldn't be less than the size
      of the image used. If so, the workaround is to generate another
      image that includes the code to configure the RAM by SPD and
      load it to L2SRAM first, then relocate the main image to RAM
      to boot up.
      
      Signed-off-by: default avatarMingkai Hu <Mingkai.hu@freescale.com>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      9a1a0aed
  19. Sep 28, 2009
  20. Sep 25, 2009
  21. Sep 24, 2009
  22. Sep 14, 2009
  23. Sep 11, 2009
Loading