1. 07 2月, 2008 1 次提交
    • G
      [POWERPC] bootwrapper: Build multiple cuImages · 25431333
      Grant Likely 提交于
      Currently, the kernel uses CONFIG_DEVICE_TREE to wrap a kernel image
      with a fdt blob which means for any given configuration only one dts
      file can be selected and so support for only one board can be built
      
      This moves the selection of the default .dts file out of the kernel
      config and into the bootwrapper makefile.  The makefile chooses which
      images to build based on the kernel config and the dts source file
      name is taken directly from the image name.  For example "cuImage.ebony"
      will use "ebony.dts" as the device tree source file.
      
      In addition, this patch allows a specific image to be requested from the
      command line by adding "cuImage.%" and "treeImage.%" targets to the list
      of valid built targets in arch/powerpc/Makefile.  This allows the default
      dts selection to be overridden.
      
      Another advantage to this change is it allows a single defconfig to be
      supplied for all boards using the same chip family and only differing in
      the device tree.
      
      Important note: This patch adds two new zImage targets; zImage.dtb.% and
      zImage.dtb.initrd.% for zImages with embedded dtb files.  Currently
      there are 5 platforms which require this: ps3, ep405, mpc885ads, ep88xc,
      adder875-redboot and ep8248e.  This patch *changes the zImage filenames*
      for those platforms.  ie. 'zImage.ps3' is now 'zImage.dtb.ps3'.
      
      This new zImage.dtb targets were added so that the .dts file could be
      part of the dependancies list for building them.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      25431333
  2. 29 1月, 2008 1 次提交
  3. 28 1月, 2008 1 次提交
  4. 25 1月, 2008 1 次提交
  5. 24 1月, 2008 3 次提交
  6. 24 12月, 2007 4 次提交
  7. 20 12月, 2007 1 次提交
  8. 11 12月, 2007 2 次提交
  9. 06 12月, 2007 1 次提交
  10. 09 10月, 2007 1 次提交
  11. 05 10月, 2007 2 次提交
  12. 04 10月, 2007 1 次提交
  13. 03 10月, 2007 3 次提交
  14. 22 9月, 2007 1 次提交
  15. 20 9月, 2007 1 次提交
  16. 13 9月, 2007 1 次提交
  17. 07 9月, 2007 2 次提交
  18. 22 8月, 2007 3 次提交
  19. 20 8月, 2007 2 次提交
  20. 10 7月, 2007 2 次提交
    • T
      [POWERPC] Create a dummy zImage if no valid platform has been selected · 4bb09281
      Tony Breeds 提交于
      This simply prevents a build error if no platform is selected.
      Signed-off-by: NTony Breeds <tony@bakeyournoodle.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      4bb09281
    • G
      [POWERPC] PS3: Bootwrapper support. · bafdb645
      Geoff Levand 提交于
      Add support to build the PS3 flash rom image and remove some unneeded
      lmb calls.
      
      The PS3's lv1 loader supports loading gzipped binary images from flash
      rom to addr zero. The loader enters the image at addr 0x100.
      
      In this implementation a bootwrapper overlay is use to arrange for the
      kernel to be loaded to addr zero and to have a suitable bootwrapper
      entry at 0x100.  To construct the rom image, 0x100 bytes from offset
      0x100 in the kernel is copied to the bootwrapper symbol
      __system_reset_kernel.  The 0x100 bytes at the bootwrapper symbol
      __system_reset_overlay is then copied to offset 0x100.  At runtime the
      bootwrapper program copies the 0x100 bytes at __system_reset_kernel to
      addr 0x100.
      
      zImage.ps3 is a wrapped image that contains a flat device tree, an lv1
      compatible entry point, and an optional initrd.  otheros.bld is the gzip
      compresed rom image built from zImage.ps3.  otheros.bld is suitable for
      programming into the PS3 boot flash memory.
      Signed-off-by: NGeoff Levand <geoffrey.levand@am.sony.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      bafdb645
  21. 25 6月, 2007 3 次提交
  22. 14 6月, 2007 2 次提交
    • D
      [POWERPC] Consolidate cuboot initialization code · 85aecac8
      David Gibson 提交于
      The various cuboot platforms (i.e. pre-device tree aware u-boot for
      83xx, 85xx and Ebony) share a certain amount of code for parsing the
      boot parameters.  To a certain extent that's inevitable, since they
      platforms have different definitions of the bd_t structure.  However,
      with some macro work and a helper function, this patch improves the
      situation a bit.
      
      In the process, this fixes a bug on Ebony, which was incorrectly
      handling the parameters passed form u-boot for the command line (the
      bug was copied from 83xx and 85xx which have subsequently been fixed).
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      85aecac8
    • D
      [POWERPC] Split low-level OF-related bootloader code into separate files · 2e601613
      David Gibson 提交于
      Currently, all OF-related code in the bootloader is contained in of.c.
      of.c also provides the platform specific things necessary to boot on
      an OF platform.
      
      However, there are platforms (such as PReP) which can include an OF
      implementation, but are not bootable as pure OF systems.  For use by
      such platforms, this patch splits out the low-level parts of the OF
      code (call_prom() and various wrappers thereof) into a new oflib.c
      file.  In addition, the code related to bootwrapper console output via
      OF are moved to a new ofconsole.c file.  Both these files are included
      in the wrapper.a library where they can be used by both full-OF and
      partial OF platforms.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      2e601613
  23. 02 6月, 2007 1 次提交
    • D
      [POWERPC] Don't use HOSTCFLAGS in BOOTCFLAGS · b610b978
      David Gibson 提交于
      In the bootwrapper code for powerpc, we include HOSTCFLAGS into the
      BOOTCFLAGS used for building the zImage wrapper code.  Since the
      wrapper code is not host code, this makes no sense.  This patch
      removes the use of HOSTCFLAGS here, instead including directly into
      BOOTCFLAGS those flags from the normal kernel CFLAGS which also make
      sense in the bootwrapper code.
      
      In particular, this makes the bootwrapper use -msoft-float, preventing
      the compiler from generating floating point instructions.  Previously,
      under some circumstances the compiler could generate floating point
      instructions in the bootwrapper which would cause exceptions on
      embedded CPUS which don't have floating point support.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Acked-by: NJosh Boyer <jwboyer@linux.vnet.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      b610b978