1. 02 6月, 2007 1 次提交
  2. 08 5月, 2007 1 次提交
  3. 02 5月, 2007 1 次提交
  4. 24 4月, 2007 1 次提交
  5. 13 4月, 2007 1 次提交
  6. 21 3月, 2007 1 次提交
  7. 13 3月, 2007 1 次提交
    • D
      [POWERPC] zImage: Cleanup and improve zImage entry point · cd197ffc
      David Gibson 提交于
      This patch re-organises the way the zImage wrapper code is entered, to
      allow more flexibility on platforms with unusual entry conditions.
      After this patch, a platform .o file has two options:
      
      1) It can define a _zimage_start, in which case the platform code gets
         control from the very beginning of execution.  In this case the
         platform code is responsible for relocating the zImage if necessary,
         clearing the BSS, performing any platform specific initialization, and
         finally calling start() to load and enter the kernel.
      
      2) It can define platform_init().  In this case the generic crt0.S
         handles initial entry, and calls platform_init() before calling
         start().  The signature of platform_init() is changed, however, to
         take up to 5 parameters (in r3..r7) as they come from the platform's
         initial loader, instead of a fixed set of parameters based on OF's
         usage.
      
         When using the generic crt0.S, the platform .o can optionally
         supply a custom stack to use, using the BSS_STACK() macro.  If this
         is not supplied, the crt0.S will assume that the loader has
         supplied a usable stack.
      
      In either case, the platform code communicates information to the
      generic code (specifically, a PROM pointer for OF systems, and/or an
      initrd image address supplied by the bootloader) via a global
      structure "loader_info".
      
      In addition the wrapper script is rearranged to ensure that the
      platform .o is always linked first.  This means that platforms where
      the zImage entry point is at a fixed address or offset, rather than
      being encoded in the binary header can be supported using option (1).
      Signed-off-by: NDavid Gibson <dwg@au1.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      cd197ffc
  8. 13 11月, 2006 1 次提交
  9. 09 11月, 2006 1 次提交
  10. 18 10月, 2006 1 次提交
  11. 28 9月, 2006 1 次提交
    • P
      [POWERPC] Create a "wrapper" script and use it in arch/powerpc/boot · 2bf11819
      Paul Mackerras 提交于
      This puts the knowledge of how to create various sorts of zImage
      wrappers into a script called "wrapper" that could be used outside of
      the kernel tree.  This changes arch/powerpc/boot so it first builds
      the files that the wrapper script needs, then runs it to create
      whatever flavours of zImage are required.
      
      This version does uImages as well.  The zImage names are changed
      slightly; zImage.pseries is the one with the PT_NOTE program header
      entry added, and zImage.pmac is the one without.  If the
      zImage.pseries gets made, it will also get hardlinked to zImage;
      otherwise, if zImage.pmac is made, it gets hardlinked to zImage.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      2bf11819