19 Nov, 2009

3 commits

  • This patch removes the duplicted implementations of the pci_master_init()
    function by introducing a weak default function for it. It can be
    overridden by a board specific version.

    Signed-off-by: Stefan Roese

    Stefan Roese
     
  • This patch removes the duplicted implementations of the pci_pre_init()
    function by introducing a weak default function for it. This weak default
    has a different implementation for some PPC variants. It can be
    overridden by a board specific version.

    Signed-off-by: Stefan Roese

    Stefan Roese
     
  • This patch removes the duplicted implementations of the pci_target_init()
    function by introducing a weak default function for it. This weak default
    has a different implementation for 440EP(x)/GR(x) PPC's. It can be
    overridden by a board specific version (e.g. PMC440, korat).

    Signed-off-by: Stefan Roese
    Acked-by: Matthias Fuchs

    Stefan Roese
     

09 Nov, 2009

1 commit


02 Nov, 2009

1 commit


31 Oct, 2009

1 commit

  • To avoid board-specific code accessing the mb862xx registers directly,
    the public function mb862xx_probe() has been introduced. Furthermore,
    the "Change of Clock Frequency" and "Set Memory I/F Mode" registers
    are now defined by CONFIG_SYS_MB862xx_CCF and CONFIG_SYS_MB862xx__MMR,
    respectively. The BSPs for the socrates and lwmon5 boards have been
    adapted accordingly.

    Signed-off-by: Wolfgang Grandegger

    Wolfgang Grandegger
     

09 Oct, 2009

1 commit


07 Oct, 2009

1 commit


03 Oct, 2009

1 commit

  • The following changes allow U-Boot to fully relocate from flash to
    RAM:
    - Remove linker scripts' .fixup sections from the .text section
    - Add -mrelocatable to PLATFORM_RELFLAGS for all boards
    - Define CONFIG_RELOC_FIXUP_WORKS for all boards

    Previously, U-Boot would partially relocate, but statically initialized
    pointers needed to be manually relocated.

    Signed-off-by: Peter Tyser

    Peter Tyser
     

28 Sep, 2009

1 commit


11 Sep, 2009

1 commit

  • This patch cleans up multiple issues of the 4xx register (mostly
    DCR, SDR, CPR, etc) definitions:

    - Change lower case defines to upper case (plb4_acr -> PLB4_ACR)
    - Change the defines to better match the names from the
    user's manuals (e.g. cprpllc -> CPR0_PLLC)
    - Removal of some unused defines

    Please test this patch intensive on your PPC4xx platform. Even though
    I tried not to break anything and tested successfully on multiple
    4xx AMCC platforms, testing on custom platforms is recommended.

    Signed-off-by: Stefan Roese

    Stefan Roese
     

13 Jun, 2009

1 commit

  • Many of the help messages were not really helpful; for example, many
    commands that take no arguments would not print a correct synopsis
    line, but "No additional help available." which is not exactly wrong,
    but not helpful either.

    Commit ``Make "usage" messages more helpful.'' changed this
    partially. But it also became clear that lots of "Usage" and "Help"
    messages (fields "usage" and "help" in struct cmd_tbl_s respective)
    were actually redundant.

    This patch cleans this up - for example:

    Before:
    => help dtt
    dtt - Digital Thermometer and Thermostat

    Usage:
    dtt - Read temperature from digital thermometer and thermostat.

    After:
    => help dtt
    dtt - Read temperature from Digital Thermometer and Thermostat

    Usage:
    dtt

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

21 Mar, 2009

1 commit

  • A recent gcc added a new unaligned rodata section called '.rodata.str1.1',
    which needs to be added the the linker script. Instead of just adding this
    one section, we use a wildcard ".rodata*" to get all rodata linker section
    gcc has now and might add in the future.

    However, '*(.rodata*)' by itself will result in sub-optimal section
    ordering. The sections will be sorted by object file, which causes extra
    padding between the unaligned rodata.str.1.1 of one object file and the
    aligned rodata of the next object file. This is easy to fix by using the
    SORT_BY_ALIGNMENT command.

    This patch has not be tested one most of the boards modified. Some boards
    have a linker script that looks something like this:

    *(.text)
    . = ALIGN(16);
    *(.rodata)
    *(.rodata.str1.4)
    *(.eh_frame)

    I change this to:

    *(.text)
    . = ALIGN(16);
    *(.eh_frame)
    *(SORT_BY_ALIGNMENT(SORT_BY_NAME(.rodata*)))

    This means the start of rodata will no longer be 16 bytes aligned.
    However, the boundary between text and rodata/eh_frame is still aligned to
    16 bytes, which is what I think the real purpose of the ALIGN call is.

    Signed-off-by: Trent Piepho

    Trent Piepho
     

17 Mar, 2009

1 commit


28 Jan, 2009

2 commits


19 Nov, 2008

1 commit

  • Most of the bss initialization loop increments 4 bytes
    at a time. And the loop end is checked for an 'equal'
    condition. Make the bss end address aligned by 4, so
    that the loop will end as expected.

    Signed-off-by: Selvamuthukumar
    Signed-off-by: Wolfgang Denk

    Selvamuthukumar
     

19 Oct, 2008

1 commit


11 Sep, 2008

1 commit


10 Jul, 2008

1 commit


03 Jul, 2008

1 commit


12 Jun, 2008

1 commit

  • This patch changes the return type of initdram() from long int to phys_size_t.
    This is required for a couple of reasons: long int limits the amount of dram
    to 2GB, and u-boot in general is moving over to phys_size_t to represent the
    size of physical memory. phys_size_t is defined as an unsigned long on almost
    all current platforms.

    This patch *only* changes the return type of the initdram function (in
    include/common.h, as well as in each board's implementation of initdram). It
    does not actually modify the code inside the function on any of the platforms;
    platforms which wish to support more than 2GB of DRAM will need to modify
    their initdram() function code.

    Build tested with MAKEALL for ppc, arm, mips, mips-el. Booted on powerpc
    MPC8641HPCN.

    Signed-off-by: Becky Bruce

    Becky Bruce
     

04 Jun, 2008

1 commit


21 May, 2008

1 commit

  • This commit gets rid of a huge amount of silly white-space issues.
    Especially, all sequences of SPACEs followed by TAB characters get
    removed (unless they appear in print statements).

    Also remove all embedded "vim:" and "vi:" statements which hide
    indentation problems.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

29 Apr, 2008

1 commit

  • As it seems the "old" ECC initialization routine by using dflush() didn't
    write all lines in the dcache back to memory on lwmon5. This could lead
    to ECC error upon Linux booting. This patch changes the program_ecc()
    routine to now use clean_dcache_range() instead of dflush().
    clean_dcache_range() uses dcbst which is exactly what we want in this
    case.

    Since dflush() is known is cause problems, this routine will be
    removed completely and replaced by clean_dcache_range() with an
    additional patch.

    Signed-off-by: Stefan Roese

    Stefan Roese
     

25 Apr, 2008

1 commit


22 Apr, 2008

1 commit

  • Limit the rate of h/w watch-dog triggering on the LWMON5 board by
    the CONFIG_WD_MAX_RATE value.

    Note that an earlier version of this patch which used microseconds
    instead of ticks dis not work. The problem was that we used
    usec2ticks() to convert microseconds into ticks. usec2ticks() uses
    get_tbclk(), which in turn calls get_sys_info(). It turns out that
    this function does a lot of prolonged operations (like divisions)
    which take too much time so we do not trigger the watchdog in time,
    and it resets the system.

    Signed-off-by: Yuri Tikhonov

    Yuri Tikhonov
     

18 Apr, 2008

1 commit


27 Mar, 2008

1 commit

  • Since all ECC related problems seem to be resolved on LWMON5, this patch
    now enables ECC support.

    We have to write the ECC bytes by zeroing and flushing in smaller
    steps, since the whole 256MByte takes too long for the external
    watchdog.

    Signed-off-by: Stefan Roese

    Stefan Roese
     

19 Mar, 2008

6 commits


13 Jan, 2008

1 commit

  • With recent toolchain versions, some boards would not build because
    or errors like this one (here for ocotea board when building with
    ELDK 4.2 beta):
    ppc_4xx-ld: section .bootpg [fffff000 -> fffff23b] overlaps section .bss [fffee900 -> fffff8ab]

    For many boards, the .bss section is big enough that it wraps around
    at the end of the address space (0xFFFFFFFF), so the problem will not
    be visible unless you use a 64 bit tool chain for development. On
    some boards however, changes to the code size (due to different
    optimizations) we bail out with section overlaps like above.

    The fix is to add the NOLOAD attribute to the .bss and .sbss
    sections, telling the linker that .bss does not consume any space in
    the image.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

11 Jan, 2008

1 commit


09 Jan, 2008

2 commits


04 Jan, 2008

1 commit