1. 13 3月, 2007 3 次提交
    • 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
    • D
      [POWERPC] zImage: Cleanup and improve prep_kernel() · 79c85419
      David Gibson 提交于
      This patch rewrites prep_kernel() in the zImage wrapper code to be
      clearer and more flexible.  Notable changes:
      
      	- Handling of the initrd image from prep_kernel() has moved
      into a new prep_initrd() function.
      	- The address of the initrd image is now added as device tree
      properties, as the kernel expects.
      	- We only copy a packaged initrd image to a new location if it
      is in danger of being clobbered when the kernel moves to its final
      location, instead of always.
      	- By default we decompress the kernel directly to address 0,
      instead of requiring it to relocate itself.  Platforms (such as OF)
      where doing this could clobber still-live firmware data structures can
      override the vmlinux_alloc hook to provide an alternate place to
      decompress the kernel.
      	- We no longer pass lots of information between functions in
      global variables.
      Signed-off-by: NDavid Gibson <dwg@au1.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      79c85419
    • D
      [POWERPC] zImage: Add more flexible gunzip convenience functions · ad9d2716
      David Gibson 提交于
      At present, arch/powerpc/boot/main.c includes a gunzip() function
      which is a convenient wrapper around zlib.  However, it doesn't
      conveniently allow decompressing part of an image to one location,
      then the remainder to a different address.
      
      This patch adds a new set of more flexible convenience wrappers around
      zlib, moving them to their own file, gunzip_util.c, in the process.
      These wrappers allow decompressing sections of the compressed image to
      different locations.  In addition, they transparently handle
      uncompressed data, avoiding special case code to handle uncompressed
      vmlinux images.
      
      The patch also converts main.c to use the new wrappers, using the new
      flexibility to avoid decompressing the vmlinux's ELF header twice as
      we did previously.  That in turn means we avoid extending our
      allocations for the vmlinux to allow space for the extra copy of the
      ELF header.
      Signed-off-by: NDavid Gibson <dwg@au1.ibm.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      ad9d2716
  2. 09 3月, 2007 14 次提交
  3. 08 3月, 2007 9 次提交
  4. 07 3月, 2007 14 次提交