1. 24 4月, 2008 1 次提交
  2. 24 12月, 2007 1 次提交
    • S
      [POWERPC] 4xx: Fix TLB 0 problem with CONFIG_SERIAL_TEXT_DEBUG · f4151b9b
      Stefan Roese 提交于
      Right now TLB entry 0 ist used as UART0 mapping for the early debug
      output (via CONFIG_SERIAL_TEXT_DEBUG). This causes problems when many
      TLB's get used upon Linux bootup (e.g. while PCIe scanning behind
      bridges and/or switches on 440SPe platforms). This will overwrite the
      TLB 0 entry and further debug output's may crash/hang the system.
      
      This patch moves the early debug UART0 TLB entry from 0 to 62 as done
      in arch/powerpc. This way it is in the "pinned" area and will not get
      overwritten. Also the arch/ppc/mm/44x_mmu.c code is now synced with the
      newer code from arch/powerpc.
      Signed-off-by: NStefan Roese <sr@denx.de>
      Signed-off-by: NJosh Boyer <jwboyer@linux.vnet.ibm.com>
      f4151b9b
  3. 15 6月, 2006 1 次提交
  4. 11 6月, 2006 1 次提交
  5. 26 4月, 2006 1 次提交
  6. 26 6月, 2005 1 次提交
  7. 17 4月, 2005 2 次提交
    • K
      [PATCH] ppc32: make usage of CONFIG_PTE_64BIT & CONFIG_PHYS_64BIT consistent · a85f6d4a
      Kumar Gala 提交于
      CONFIG_PTE_64BIT & CONFIG_PHYS_64BIT are not currently consistently used in
      the code base.  Fixed up the usage such that CONFIG_PTE_64BIT is used when we
      have a 64-bit PTE regardless of physical address width.  CONFIG_PHYS_64BIT is
      used if the physical address width is larger than 32-bits, regardless of PTE
      size.
      
      These changes required a few sub-arch specific ifdef's to be fixed and the
      introduction of a physical address format string.
      Signed-off-by: NKumar Gala <kumar.gala@freescale.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      a85f6d4a
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4