1. 17 Feb, 2009 7 commits
  2. 12 Feb, 2009 2 commits
    • Adam Graham's avatar
      ppc4xx: Autocalibration can set RDCC to over aggressive value. · c645012a
      Adam Graham authored
      
      
      The criteria of the AMCC SDRAM Controller DDR autocalibration
      U-Boot code is to pick the largest passing write/read/compare
      window that also has the smallest SDRAM_RDCC.[RDSS] Read Sample
      Cycle Select value.
      
      On some Kilauea boards the DDR autocalibration algorithm can
      find a large passing write/read/compare window with a small
      SDRAM_RDCC.[RDSS] aggressive value of Read Sample Cycle Select
      value "T1 Sample".
      
      This SDRAM_RDCC.[RDSS] Read Sample Cycle Select value of
      "T1 Sample" proves to be to aggressive when later on U-Boot
      relocates into DDR memory and executes.
      
      The memory traces on the Kilauea board are short so on some
      Kilauea boards the SDRAM_RDCC.[RDSS] Read Sample Cycle Select
      value of "T1 Sample" shows up as a potentially valid value for
      the DDR autocalibratiion algorithm.
      
      The fix is to define a weak default function which provides
      the minimum SDRAM_RDCC.[RDSS] Read Sample Cycle Select value
      to accept for DDR autocalibration.  The default will be the
      "T2 Sample" value.  A board developer who has a well defined
      board and chooses to be more aggressive can always provide
      their own board specific string function with the more
      aggressive "T1 Sample" value or stick with the default
      minimum SDRAM_RDCC.[RDSS] value of "T2".
      
      Also put in a autocalibration loop fix for case where current
      write/read/compare passing window size is the same as a prior
      window size, then in this case choose the write/read/compare
      result that has the associated smallest RDCC T-Sample value.
      Signed-off-by: default avatarAdam Graham <agraham@amcc.com>
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      c645012a
    • Stefan Roese's avatar
      ppc4xx: Fix problem with CONFIG_MAX_MEM_MAPPED in include/asm-ppc/config.h · 2ede879f
      Stefan Roese authored
      
      
      CONFIG_SDRAM_PPC4xx_IBM_DDR2 is not set when include/asm-ppc/config.h is
      included. So for katmai, CONFIG_MAX_MEM_MAPPED will get set to 256MB.
      
      It makes perfect sense to set CONFIG_MAX_MEM_MAPPED to 2GB for all PPC4xx
      boards right now.
      Signed-off-by: default avatarStefan Roese <sr@denx.de>
      2ede879f
  3. 09 Feb, 2009 4 commits
  4. 03 Feb, 2009 2 commits
  5. 23 Jan, 2009 4 commits
  6. 22 Jan, 2009 1 commit
  7. 20 Dec, 2008 4 commits
  8. 16 Dec, 2008 1 commit
  9. 15 Dec, 2008 1 commit
    • Kumar Gala's avatar
      Introduce virt_to_phys() · 65e43a10
      Kumar Gala authored
      
      
      virt_to_phys() returns the physical address given a virtual. In most
      cases this will be just the input value as the vast majority of
      systems run in a 1:1 mode.
      
      However in systems that are not running this way it should report the
      physical address or ~0 if no mapping exists for the given virtual
      address.
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      65e43a10
  10. 04 Dec, 2008 2 commits
  11. 21 Nov, 2008 1 commit
  12. 29 Oct, 2008 1 commit
  13. 27 Oct, 2008 1 commit
  14. 24 Oct, 2008 1 commit
  15. 21 Oct, 2008 3 commits
  16. 18 Oct, 2008 5 commits