1. 12 2月, 2008 1 次提交
    • M
      Use proper abstractions in quirk_intel_irqbalance · 9585ca02
      Matthew Wilcox 提交于
      Since we may not have a pci_dev for the device we need to access, we can't
      use pci_read_config_word.  But raw_pci_read is an internal implementation
      detail; it's better to use the architected pci_bus_read_config_word
      interface.  Using PCI_DEVFN instead of a mysterious constant helps
      reassure everyone that we really do intend to access device 8.
      
      [ Thanks to Grant Grundler for pointing out to me that this is exactly
        what the write immediately above this is doing -- enabling device 8 to
        respond to config space cycles.
      					- Matthew
      
        Grant also says:
      
      	"Can you also add a comment which points at the Intel
      	 documentation?
      
      	 The 'Intel E7320 Memory Controller Hub (MCH) Datasheet' at
      
      	  http://download.intel.com/design/chipsets/datashts/30300702.pdf
      
      	 Page 69 documents register F4h (DEVPRES1).
      
      	 And I just doubled checked that the 0xf4 register value is
      	 restored later in the quirk (obvious when you look at the code
      	 but not from the patch"
      
        so here it is.
      					 - Linus ]
      Signed-off-by: NMatthew Wilcox <willy@linux.intel.com>
      Acked-by: NGrant Grundler <grundler@parisc-linux.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9585ca02
  2. 11 2月, 2008 1 次提交
  3. 07 2月, 2008 1 次提交
  4. 02 2月, 2008 1 次提交
  5. 30 1月, 2008 1 次提交
  6. 24 10月, 2007 2 次提交
  7. 20 10月, 2007 3 次提交
  8. 13 10月, 2007 4 次提交
  9. 11 10月, 2007 1 次提交
  10. 08 7月, 2007 1 次提交
  11. 03 5月, 2007 2 次提交
  12. 10 12月, 2006 1 次提交
  13. 07 12月, 2006 1 次提交
  14. 01 7月, 2006 1 次提交
  15. 19 1月, 2006 1 次提交
  16. 17 4月, 2005 1 次提交
    • 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