An error occurred fetching the project authors.
  1. 04 Aug, 2008 1 commit
  2. 27 Apr, 2008 1 commit
  3. 16 Apr, 2008 1 commit
    • Kumar Gala's avatar
      [POWERPC] Move phys_addr_t definition into asm/types.h · d04ceb3f
      Kumar Gala authored
      Moved phys_addr_t out of mmu-*.h and into asm/types.h so we can use it in
      places that before would have caused recursive includes.
      
      For example to use phys_addr_t in <asm/page.h> we would have included
      <asm/mmu.h> which would have possibly included <asm/mmu-hash64.h> which
      includes <asm/page.h>.  Wheeee recursive include.
      
      CONFIG_PHYS_64BIT is a bit counterintuitive in light of ppc64 systems
      and thus the config option is only used for ppc32 systems with >32-bit
      physical addresses (44x, 85xx, 745x, etc.).
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      d04ceb3f
  4. 17 May, 2007 1 commit
    • David Gibson's avatar
      [POWERPC] Remove fixup_bigphys_addr() for arch/powerpc to avoid link error · e3d67b66
      David Gibson authored
      There are no actual implementations of fixup_bigphys_addr() in
      arch/powerpc, and with a 64-bit aware ioremap() and so forth, it
      should no longer be necessary.  This patch removes the last dregs of
      fixup_bigphys_addr() from arch/powerpc.
      
      In fact, the only reason this hasn't caused link errors already is
      that nobody must have tried using one of the small number of drivers
      using io_remap_pfn_range() on one of the small number of platforms
      which are 32-bit but define CONFIG_PHYS_64BIT.  Nonetheless this fixes
      a bug, and should go into 2.6.22.
      Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: default avatarPaul Mackerras <paulus@samba.org>
      e3d67b66
  5. 08 May, 2007 1 commit
  6. 02 May, 2007 1 commit