1. 23 May, 2012 1 commit
  2. 22 May, 2012 4 commits
  3. 18 May, 2012 1 commit
  4. 15 May, 2012 2 commits
  5. 25 Apr, 2012 10 commits
  6. 18 Mar, 2012 5 commits
  7. 03 Mar, 2012 1 commit
  8. 15 Feb, 2012 2 commits
  9. 13 Jan, 2012 1 commit
  10. 10 Jan, 2012 1 commit
  11. 13 Dec, 2011 1 commit
  12. 12 Dec, 2011 1 commit
    • Kumar Gala's avatar
      powerpc/bootm: Flush ramdisk and device tree image when booting on MP · 3b200110
      Kumar Gala authored
      We already flush the kernel image after we've loaded it to ensure
      visiblity to the other cores.  We need to do the same thing for the
      ramdisk and device tree images.  In AMP boot scenarios we might not be
      HW cache coherent with the secondary core that we are loading and
      setting the ramdisk and device tree up for.  Thus we need to ensure
      we've flushed the regions of memory utilized by ramdisk and device tree
      so the loadding and any modifications (from decompression or fdt updates)
      are made visible to the secondary cores.
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      3b200110
  13. 07 Dec, 2011 2 commits
    • Kyle Moffett's avatar
      powerpc: Minimal private libgcc to build on Debian · 01baa056
      Kyle Moffett authored
      Standard Debian powerpc and powerpcspe systems only include hard-float
      libgcc in their native compilers, which causes scary build warnings when
      building U-Boot.
      
      Debian and other PowerPC-supporting distributions used to provide libgcc
      and other libraries in a "nof" (soft-float) form in the "multilib"
      packages.  As they were completely unused by the distribution and
      therefore tended to be very buggy it was decided to save some time on
      the part of the maintainers and build-servers by removing them.
      
      Admittedly, right now the linker warnings do not indicate any problems,
      as the included routines do not use any floating point at all.
      
      The concern is that if floating-point code were ever added it might
      cause hard-float code to be unexpectedly included in U-Boot without
      generating a hard error.  This would cause unexplained crashes or
      indeterminate results at runtime.
      
      The easiest way to resolve this is to borrow the routines that U-Boot
      needs from the Linux kernel, which has the same issue.
      
      Specifically, the routines are: _ashldi3(), _ashrdi3(), and _lshrdi3().
      They were borrowed from arch/powerpc/kernel/misc_32.S as of v2.6.38-rc5,
      commit 85e2efbb1db9a18d218006706d6e4fbeb0216213, and are GPLv2+.
      
      The Makefile framework was copied from the U-Boot ARM port.
      Signed-off-by: default avatarKyle Moffett <Kyle.D.Moffett@boeing.com>
      Cc: Wolfgang Denk <wd@denx.de>
      Cc: Kim Phillips <kim.phillips@freescale.com>
      Cc: Andy Fleming <afleming@gmail.com>
      Cc: Kumar Gala <kumar.gala@freescale.com>
      Cc: Stefan Roese <sr@denx.de>
      01baa056
    • Stefan Roese's avatar
      ppc4xx: Remove usbdev.c · ce2acd37
      Stefan Roese authored
      As this "driver" doesn't seem to be really used, let's remove
      it completely.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      ce2acd37
  14. 01 Dec, 2011 1 commit
  15. 29 Nov, 2011 7 commits