26 Nov, 2013

2 commits


01 Nov, 2013

1 commit


15 Oct, 2013

1 commit


24 Jul, 2013

1 commit


28 Nov, 2012

1 commit

  • There were a number of shared files that were using
    CONFIG_SYS_MPC85xx_DDR_ADDR, or CONFIG_SYS_MPC86xx_DDR_ADDR, and
    several variants (DDR2, DDR3). A recent patchset added
    85xx-specific ones to code which was used by 86xx systems.
    After reviewing places where these constants were used, and
    noting that the type definitions of the pointers assigned to
    point to those addresses were the same, the cleanest approach
    to fixing this problem was to unify the namespace for the
    85xx, 83xx, and 86xx DDR address definitions.

    This patch does:

    s/CONFIG_SYS_MPC8.xx_DDR/CONFIG_SYS_MPC8xxx_DDR/g

    All 85xx, 86xx, and 83xx have been built with this change.

    Signed-off-by: Andy Fleming
    Tested-by: Andy Fleming
    Acked-by: Kim Phillips

    Andy Fleming
     

05 Nov, 2012

1 commit

  • fsl_corenet_serdes.c:485:6: warning: symbol '__soc_serdes_init' was not declared. Should it be static?
    cpu_init.c:185:6: warning: symbol 'invalidate_cpc' was not declared. Should it be static?
    bcsr.c:28:27: warning: non-ANSI function declaration of function 'enable_8568mds_duart'
    bcsr.c:39:33: warning: non-ANSI function declaration of function 'enable_8568mds_flash_write'
    bcsr.c:46:34: warning: non-ANSI function declaration of function 'disable_8568mds_flash_write'
    bcsr.c:53:29: warning: non-ANSI function declaration of function 'enable_8568mds_qe_mdio'
    bcsr.c:28:33: warning: non-ANSI function declaration of function 'enable_8569mds_flash_write'
    bcsr.c:33:34: warning: non-ANSI function declaration of function 'disable_8569mds_flash_write'
    bcsr.c:38:28: warning: non-ANSI function declaration of function 'enable_8569mds_qe_uec'
    bcsr.c:63:47: warning: non-ANSI function declaration of function 'disable_8569mds_brd_eeprom_write_protect'
    ngpixis.c:245:1: error: directive in argument list
    ngpixis.c:247:1: error: directive in argument list

    Signed-off-by: Kim Phillips

    Kim Phillips
     

29 Jul, 2012

1 commit


11 Nov, 2011

1 commit


16 Oct, 2011

1 commit

  • The top level Makefile does not do any recursion into subdirs when
    cleaning, so these clean/distclean targets in random arch/board dirs
    never get used. Punt them all.

    MAKEALL didn't report any errors related to this that I could see.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

21 Apr, 2011

1 commit

  • The fsl_phy_enet_if enum was, essentially, the phy_interface_t enum.
    This meant that drivers which used fsl_phy_enet_if to deal with
    PHY interfaces would have to convert between the two (or we would have
    to have them mirror each other, and deal with the ensuing maintenance
    headache). Instead, we switch all clients of fsl_phy_enet_if over to
    phy_interface_t, which should become the standard, anyway.

    Signed-off-by: Andy Fleming
    Acked-by: Detlev Zundel

    Andy Fleming
     

04 Apr, 2011

3 commits


14 Jan, 2011

4 commits

  • Signed-off-by: Kumar Gala

    Kumar Gala
     
  • Remove duplicated code in MPC8569MDS board and utilize the common
    fsl_pcie_init_board(). We also now dynamically setup the LAWs for PCI
    controllers based on which PCIe controllers are enabled.

    Signed-off-by: Kumar Gala

    Kumar Gala
     
  • Correct initdram to use phys_size_t to represent the size of
    dram; instead of changing this all over the place, and correcting
    all the other random errors I've noticed, create a
    common initdram that is used by all non-corenet 85xx parts. Most
    of the initdram() functions were identical, with 2 common differences:

    1) DDR tlbs for the fixed_sdram case were set up in initdram() on
    some boards, and were part of the tlb_table on others. I have
    changed them all over to the initdram() method - we shouldn't
    be accessing dram before this point so they don't need to be
    done sooner, and this seems cleaner.

    2) Parts that require the DDR11 erratum workaround had different
    implementations - I have adopted the version from the Freescale
    errata document. It also looks like some of the versions were
    buggy, and, depending on timing, could have resulted in the
    DDR controller being disabled. This seems bad.

    The xpedite boards had a common/fsl_8xxx_ddr.c; with this
    change only the 517 board uses this so I have moved the ddr code
    into that board's directory in xpedite517x.c

    Signed-off-by: Becky Bruce
    Tested-by: Paul Gortmaker
    Signed-off-by: Kumar Gala

    Becky Bruce
     
  • Now that we have serdes support for all 85xx/86xx/Pxxx chips we can
    replace the is_fsl_pci_cfg() code with the is_serdes_configured().

    Signed-off-by: Kumar Gala

    Kumar Gala
     

18 Nov, 2010

1 commit

  • Before this commit, weak symbols were not overridden by non-weak symbols
    found in archive libraries when linking with recent versions of
    binutils. As stated in the System V ABI, "the link editor does not
    extract archive members to resolve undefined weak symbols".

    This commit changes all Makefiles to use partial linking (ld -r) instead
    of creating library archives, which forces all symbols to participate in
    linking, allowing non-weak symbols to override weak symbols as intended.
    This approach is also used by Linux, from which the gmake function
    cmd_link_o_target (defined in config.mk and used in all Makefiles) is
    inspired.

    The name of each former library archive is preserved except for
    extensions which change from ".a" to ".o". This commit updates
    references accordingly where needed, in particular in some linker
    scripts.

    This commit reveals board configurations that exclude some features but
    include source files that depend these disabled features in the build,
    resulting in undefined symbols. Known such cases include:
    - disabling CMD_NET but not CMD_NFS;
    - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.

    Signed-off-by: Sebastien Carlier

    Sebastien Carlier
     

15 Nov, 2010

1 commit

  • Previously boards used a variety of indentations, newline styles, and
    colon styles for the PCI information that is printed on bootup. This
    patch unifies the style to look like:

    ...
    NAND: 1024 MiB
    PCIE1: connected as Root Complex
    Scanning PCI bus 01
    04 01 8086 1010 0200 00
    04 01 8086 1010 0200 00
    03 00 10b5 8112 0604 00
    02 01 10b5 8518 0604 00
    02 02 10b5 8518 0604 00
    08 00 1957 0040 0b20 00
    07 00 10b5 8518 0604 00
    09 00 10b5 8112 0604 00
    07 01 10b5 8518 0604 00
    07 02 10b5 8518 0604 00
    06 00 10b5 8518 0604 00
    02 03 10b5 8518 0604 00
    01 00 10b5 8518 0604 00
    PCIE1: Bus 00 - 0b
    PCIE2: connected as Root Complex
    Scanning PCI bus 0d
    0d 00 1957 0040 0b20 00
    PCIE2: Bus 0c - 0d
    In: serial
    ...

    Signed-off-by: Peter Tyser
    CC: wd@denx.de
    CC: sr@denx.de
    CC: galak@kernel.crashing.org

    Peter Tyser
     

20 Oct, 2010

1 commit


19 Oct, 2010

3 commits

  • Clean up Makefile, and drop a lot of the config.mk files on the way.

    We now also automatically pick all boards that are listed in
    boards.cfg (and with all configurations), so we can drop the redundant
    entries from MAKEALL to avoid building these twice.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     
  • The change is currently needed to be able to remove the board
    configuration scripting from the top level Makefile and replace it by
    a simple, table driven script.

    Moving this configuration setting into the "CONFIG_*" name space is
    also desirable because it is needed if we ever should move forward to
    a Kconfig driven configuration system.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     
  • When planning for more generalization and Makefile cleanup it became
    obvious that the introduction of a separate CONFIG_MK_ name space for
    config options that were set through scripting in the Makefile was
    not a good idea.

    Originally the idea was to provide a script-free approach to supply
    configuration options - there was no real need for a separate name
    space. But when we now convert the existing Makefile entries to make
    use of this approach, it would mean that we have to touch a large
    number of board config files and add #ifdef / #define sequences to
    "convert" from the CONFIG_MK_ to the CONFIG_ name space.

    It seems much cleaner to get rid of this somewhat arbitrary _MK
    string now for the few boards that actually use it.

    Signed-off-by: Wolfgang Denk
    Acked-by: Mike Frysinger

    Wolfgang Denk
     

07 Oct, 2010

2 commits

  • Enable half drive strength, set RTT to 60Ohm and set write leveling override.

    Signed-off-by: Haiying Wang
    Signed-off-by: Kumar Gala

    Haiying Wang
     
  • The original code maps boot flash as non-cacheable region. When calling
    relocate_code in flash to copy u-boot from flash to ddr, every loop copy command
    is read from flash. The flash read speed will be the bottleneck, which consuming
    long time to do this operation. To resovle this, map the boot flash as
    write-through cache via tlb. And set tlb to remap the flash after code
    executing in ddr, to confirm flash erase operation properly done.

    Signed-off-by: Kai.Jiang
    Signed-off-by: Kumar Gala

    Haiying Wang
     

20 Jul, 2010

1 commit


16 Jul, 2010

1 commit

  • Currently, 83xx, 86xx, and 85xx have a lot of duplicated code
    dedicated to defining and manipulating the LBC registers. Merge
    this into a single spot.

    To do this, we have to decide on a common name for the data structure
    that holds the lbc registers - it will now be known as fsl_lbc_t, and we
    adopt a common name for the immap layouts that include the lbc - this was
    previously known as either im_lbc or lbus; use the former.

    In addition, create accessors for the BR/OR regs that use in/out_be32
    and use those instead of the mismash of access methods currently in play.

    I have done a successful ppc build all and tested a board or two from
    each processor family.

    Signed-off-by: Becky Bruce
    Acked-by: Kim Phillips
    Signed-off-by: Kumar Gala

    Becky Bruce
     

13 Apr, 2010

1 commit

  • The CPUDIR variable points to the location of a target's CPU directory.
    Currently, it is set to cpu/$CPU. However, using $CPUDIR will allow for
    more flexibility in the future. It lays the groundwork for reorganizing
    U-Boot's directory structure to support a layout such as:

    arch/$ARCH/cpu/$CPU/* (architecture with multiple CPU types)
    arch/$ARCH/cpu/* (architecture with one CPU type)

    Signed-off-by: Peter Tyser

    Peter Tyser
     

28 Jan, 2010

1 commit


26 Jan, 2010

1 commit


18 Jan, 2010

1 commit


06 Jan, 2010

2 commits


27 Oct, 2009

6 commits