1. 25 1月, 2014 1 次提交
  2. 22 1月, 2014 1 次提交
  3. 26 11月, 2013 1 次提交
  4. 05 11月, 2013 2 次提交
  5. 24 7月, 2013 1 次提交
  6. 23 7月, 2013 1 次提交
  7. 21 6月, 2013 1 次提交
  8. 08 6月, 2013 1 次提交
    • G
      pci: introduce CONFIG_PCI_INDIRECT_BRIDGE option · 842033e6
      Gabor Juhos 提交于
      The pci_indirect.c file is always compiled when
      CONFIG_PCI is defined although the indirect PCI
      bridge support is not needed by every board.
      
      Introduce a new CONFIG_PCI_INDIRECT_BRIDGE
      config option and only compile indirect PCI
      bridge support if this options is enabled.
      
      Also add the new option into the configuration
      files of the boards which needs that.
      
      Compile tested for powerpc, x86, arm and nds32.
      MAKEALL results:
      
      powerpc:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 641
        Boards with warnings but no errors: 2 ( ELPPC MPC8323ERDB )
        ----------------------------------------------------------
        Note: the warnings for ELPPC and MPC8323ERDB are present even
        without the actual patch.
      
      x86:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 1
        ----------------------------------------------------------
      
      arm:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 311
        ----------------------------------------------------------
      
      nds32:
        --------------------- SUMMARY ----------------------------
        Boards compiled: 3
        ----------------------------------------------------------
      
      Cc: Tom Rini <trini@ti.com>
      Cc: Daniel Schwierzeck <daniel.schwierzeck@googlemail.com>
      Signed-off-by: NGabor Juhos <juhosg@openwrt.org>
      842033e6
  9. 28 11月, 2012 1 次提交
  10. 07 7月, 2012 1 次提交
  11. 21 6月, 2012 1 次提交
  12. 15 5月, 2012 2 次提交
  13. 29 11月, 2011 1 次提交
    • T
      powerpc/85xx: clean up and document the QE/FMAN microcode macros · f2717b47
      Timur Tabi 提交于
      Several macros are used to identify and locate the microcode binary image
      that U-boot needs to upload to the QE or Fman.  Both the QE and the Fman
      use the QE Firmware binary format to package their respective microcode data,
      which is why the same macros are used for both.  A given SOC will only have
      a QE or an Fman, so this is safe.
      
      Unfortunately, the current macro definition and usage has inconsistencies.
      For example, CONFIG_SYS_FMAN_FW_ADDR was used to define the address of Fman
      firmware in NOR flash, but CONFIG_SYS_QE_FW_IN_NAND contains the address
      of NAND.  There's no way to know by looking at a variable how it's supposed
      to be used.
      
      In the future, the code which uploads QE firmware and Fman firmware will
      be merged.
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      f2717b47
  14. 22 10月, 2011 1 次提交
  15. 06 10月, 2011 1 次提交
  16. 30 9月, 2011 2 次提交
    • R
      powerpc/85xx: Add networking support to P1023RDS · fe1a1da0
      Roy Zang 提交于
      The P1023 has two 1G ethernet controllers the first can run in
      SGMII, RGMII, or RMII.  The second can only do SGMII & RGMII.
      
      We need to setup a for SoC & board registers based on our various
      configuration for ethernet to function properly on the board.
      
      Removed CONFIG_SYS_FMAN_FW as its not used anywhere.
      Signed-off-by: NRoy Zang <tie-fei.zang@freescale.com>
      Signed-off-by: NHaiying Wang <Haiying.Wang@freescale.com>
      Signed-off-by: NLei Xu <B33228@freescale.com>
      Signed-off-by: NIoana Radulescu <ruxandra.radulescu@freescale.com>
      Signed-off-by: NShaohui Xie <b21989@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      fe1a1da0
    • T
      powerpc/85xx: introduce and document CONFIG_SYS_CCSRBAR macros · e46fedfe
      Timur Tabi 提交于
      Introduce the CONFIG_SYS_CCSRBAR_PHYS_HIGH and CONFIG_SYS_CCSRBAR_PHYS_LOW
      macros, which contain the high and low portions of CONFIG_SYS_CCSRBAR_PHYS.
      This is necessary for the assembly-language code that relocates CCSR, since
      the assembler does not understand 64-bit constants.
      
      CONFIG_SYS_CCSRBAR_PHYS is automatically defined from the
      CONFIG_SYS_CCSRBAR_PHYS_HIGH and CONFIG_SYS_CCSRBAR_PHYS_LOW macros, so it
      should not be defined in a board header file.  Similarly,
      CONFIG_SYS_CCSRBAR_DEFAULT is defined for each SOC in config_mpc85xx.h, so
      it should also not be defined in the board header file.
      
      CONFIG_SYS_CCSR_DO_NOT_RELOCATE is a "short-cut" macro that guarantees that
      CONFIG_SYS_CCSRBAR_PHYS is set to the same value as CONFIG_SYS_CCSRBAR_DEFAULT,
      and so CCSR will not be relocated.
      
      Since CONFIG_SYS_CCSRBAR_DEFAULT is locked to a fixed value, multi-stage U-Boot
      builds (e.g. NAND) are required to relocate CCSR only during the last stage
      (i.e. the "real" U-Boot).  All other stages should define
      CONFIG_SYS_CCSR_DO_NOT_RELOCATE to ensure that CCSR is not relocated.
      
      README is updated with descriptions of all the CONFIG_SYS_CCSRBAR_xxx macros.
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      e46fedfe
  17. 29 7月, 2011 1 次提交
    • K
      powerpc/85xx: Fix build failure for P1023RDS · 74d9d523
      Kumar Gala 提交于
      When we added the fman fdt fixup we forgot to fixup the P1023RDS
      platform.  So we would get:
      
      fdt.c: In function 'fdt_fixup_fman_firmware':
      fdt.c:465:15: error: 'CONFIG_SYS_FMAN_FW_LENGTH' undeclared (first use in this function)
      fdt.c:465:15: note: each undeclared identifier is reported only once for each function it appears in
      
      Add the needed #defines in P1023RDS.h to fix this.
      Signed-off-by: NKumar Gala <galak@kernel.crashing.org>
      74d9d523
  18. 12 7月, 2011 1 次提交