1. 09 Sep, 2008 2 commits
  2. 12 Aug, 2008 1 commit
  3. 10 Aug, 2008 1 commit
  4. 09 Jul, 2008 1 commit
  5. 10 Jun, 2008 1 commit
  6. 23 May, 2008 1 commit
  7. 10 May, 2008 1 commit
  8. 09 May, 2008 1 commit
  9. 29 Apr, 2008 1 commit
    • Guennadi Liakhovetski's avatar
      net: make ARP timeout configurable · 40cb90ee
      Guennadi Liakhovetski authored
      Currently the timeout waiting for an ARP reply is hard set to 5 seconds.
      On i.MX31ADS due to a hardware "strangeness" up to four first IP packets
      to the boards get lost, which typically are ARP replies. By configuring
      the timeout to a lower value we significantly improve the first network
      transfer time on this board. The timeout is specified in milliseconds,
      later internally it is converted to deciseconds, because it has to be
      converted to hardware ticks, and CFG_HZ ranges from 900 to 27000000 on
      different boards.
      Signed-off-by: default avatarGuennadi Liakhovetski <lg@denx.de>
      Signed-off-by: default avatarBen Warren <biggerbadderben@gmail.com>
  10. 18 Apr, 2008 3 commits
  11. 12 Apr, 2008 1 commit
  12. 08 Apr, 2008 3 commits
  13. 01 Apr, 2008 1 commit
  14. 30 Mar, 2008 2 commits
  15. 28 Mar, 2008 1 commit
  16. 27 Mar, 2008 1 commit
    • Stefan Roese's avatar
      ppc: Add CFG_MEM_TOP_HIDE option to hide memory area that doesn't get "touched" · 14f73ca6
      Stefan Roese authored
      If CFG_MEM_TOP_HIDE is defined in the board config header, this specified
      memory area will get subtracted from the top (end) of ram and won't get
      "touched" at all by U-Boot. By fixing up gd->ram_size the Linux kernel
      should gets passed the now "corrected" memory size and won't touch it
      either. This should work for arch/ppc and arch/powerpc. Only Linux board
      ports in arch/powerpc with bootwrapper support, which recalculate the
      memory size from the SDRAM controller setup, will have to get fixed
      in Linux additionally.
      This patch enables this config option on some PPC440EPx boards as a workaround
      for the CHIP 11 errata. Here the description from the AMCC documentation:
      CHIP_11: End of memory range area restricted access.
      Category: 3
      The 440EPx DDR controller does not acknowledge any
      transaction which is determined to be crossing over the
      end-of-memory-range boundary, even if the starting address is
      within valid memory space. Any such transaction from any PLB4
      master will result in a PLB time-out on PLB4 bus.
      In case of such misaligned bursts, PLB4 masters will not
      retrieve any data at all, just the available data up to the
      end of memory, especially the 440 CPU. For example, if a CPU
      instruction required an operand located in memory within the
      last 7 words of memory, the DCU master would burst read 8
      words to update the data cache and cross over the
      end-of-memory-range boundary. Such a DCU read would not be
      answered by the DDR controller, resulting in a PLB4 time-out
      and ultimately in a Machine Check interrupt. The data would
      be inaccessible to the CPU.
      Forbid any application to access the last 256 bytes of DDR
      memory. For example, make your operating system believe that
      the last 256 bytes of DDR memory are absent. AMCC has a patch
      that does this, available for Linux.
      This patch sets CFG_MEM_TOP_HIDE for the following 440EPx boards:
      lwmon5, korat, sequoia
      The other remaining 440EPx board were intentionally not included
      since it is not clear to me, if they use the end of ram for some
      other purpose. This is unclear, since these boards have CONFIG_PRAM
      defined and even comments like this:
      /* esd expects pram at end of physical memory.
       * So no logbuffer at the moment.
      It is strongly recommended to not use the last 256 bytes on those
      boards too. Patches from the board maintainers are welcome.
      Signed-off-by: Stefan Roese's avatarStefan Roese <sr@denx.de>
  17. 26 Mar, 2008 3 commits
  18. 19 Mar, 2008 1 commit
  19. 16 Mar, 2008 1 commit
  20. 12 Mar, 2008 3 commits
  21. 14 Feb, 2008 1 commit
    • Wolfgang Denk's avatar
      PPC: Use r2 instead of r29 as global data pointer · e7670f6c
      Wolfgang Denk authored
      R29 was an unlucky choice as with recent toolchains (gcc-4.2.x) gcc
      will refuse to use load/store multiple insns; instead, it issues a
      list of simple load/store instructions upon function entry and exit,
      resulting in bigger code size, which in turn makes the build for a
      few boards fail.
      Use r2 instead.
      Signed-off-by: Wolfgang Denk's avatarWolfgang Denk <wd@denx.de>
  22. 05 Feb, 2008 1 commit
  23. 18 Jan, 2008 1 commit
  24. 17 Jan, 2008 4 commits
  25. 11 Jan, 2008 1 commit
  26. 09 Jan, 2008 2 commits