1. 09 2月, 2008 9 次提交
  2. 08 2月, 2008 2 次提交
  3. 07 2月, 2008 11 次提交
  4. 06 2月, 2008 4 次提交
  5. 05 2月, 2008 1 次提交
  6. 29 1月, 2008 2 次提交
  7. 23 1月, 2008 1 次提交
  8. 22 1月, 2008 1 次提交
    • S
      [SPARC64]: Fix of section mismatch warnings. · a1f35ba3
      Sam Ravnborg 提交于
      Fix following Section mismatch warning in sparc64:
      
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x13dec): Section mismatch: reference to .devinit.text:pci_scan_one_pbm (between 'psycho_scan_bus' and 'psycho_pbm_init')
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x14b58): Section mismatch: reference to .devinit.text:pci_scan_one_pbm (between 'sabre_scan_bus' and 'sabre_init')
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x15ea4): Section mismatch: reference to .devinit.text:pci_scan_one_pbm (between 'schizo_scan_bus' and 'schizo_pbm_init')
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x17780): Section mismatch: reference to .devinit.text:pci_scan_one_pbm (between 'pci_sun4v_scan_bus' and 'pci_sun4v_get_head')
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x17d5c): Section mismatch: reference to .devinit.text:pci_scan_one_pbm (between 'pci_fire_scan_bus' and 'pci_fire_get_head')
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x23860): Section mismatch: reference to .devinit.text:vio_dev_release (between 'vio_create_one' and 'vio_add')
      WARNING: arch/sparc64/kernel/built-in.o(.text+0x23868): Section mismatch: reference to .devinit.text:vio_dev_release (between 'vio_create_one' and 'vio_add')
      
      The pci_* were all missing __init annotations.
      For the vio.c case it was a function with a wrong annotation which was removed.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a1f35ba3
  9. 17 1月, 2008 1 次提交
  10. 13 1月, 2008 1 次提交
  11. 27 12月, 2007 1 次提交
  12. 21 12月, 2007 1 次提交
  13. 13 12月, 2007 1 次提交
    • D
      [SPARC64]: Fix two kernel linear mapping setup bugs. · 8f361453
      David S. Miller 提交于
      This was caught and identified by Greg Onufer.
      
      Since we setup the 256M/4M bitmap table after taking over the trap
      table, it's possible for some 4M mapping to get loaded in the TLB
      beforhand which later will be 256M mappings.
      
      This can cause illegal TLB multiple-match conditions.  Fix this by
      setting up the bitmap before we take over the trap table.
      
      Next, __flush_tlb_all() was not doing anything on hypervisor
      platforms.  Fix by adding sun4v_mmu_demap_all() and calling it.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8f361453
  14. 12 12月, 2007 1 次提交
  15. 07 12月, 2007 1 次提交
  16. 05 12月, 2007 2 次提交