1. 10 10月, 2006 1 次提交
  2. 26 9月, 2006 1 次提交
  3. 22 9月, 2006 2 次提交
    • N
      [POWERPC] Demacrofy arch/powerpc/platforms/maple/pci.c · cc9881ce
      Nathan Lynch 提交于
      Noticed that the U3_*CFA macros have some typos:
      
      #define U3_HT_CFA0(devfn, off)		\
      		((((unsigned long)devfn) << 8) | offset)
      
      (refers to offset rather than off)
      
      #define U3_AGP_CFA0(devfn, off)	\
      	((1 << (unsigned long)PCI_SLOT(dev_fn)) \
      	| (((unsigned long)PCI_FUNC(dev_fn)) << 8) \
      
      (refers to dev_fn rather than devfn)
      
      Things happen to work, but there doesn't seem to be any reason these
      shouldn't be functions.  Overall behavior should be unchanged.
      Signed-off-by: NNathan Lynch <ntl@pobox.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      cc9881ce
    • N
      [POWERPC] Maple U3 HT - reject inappropriate config space access · d608df5c
      Nathan Lynch 提交于
      When there is a PCI-X mode 2 capable device behind the HT<->PCI-X
      bridge, the pci core decides that the device has the extended 4K
      config space, even though the bus is not operating in mode 2.  This is
      because the u3_ht pci ops silently accept offsets greater than 255 but
      use only the 8 least significant bits, which means reading at offset
      0x100 gets the data at offset 0x0, and causes confusion for lspci.
      
      Reject accesses to configuration space offsets greater than 255.
      Signed-off-by: NNathan Lynch <ntl@pobox.com>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      d608df5c
  4. 31 7月, 2006 1 次提交
  5. 03 7月, 2006 1 次提交
    • B
      [POWERPC] Add new interrupt mapping core and change platforms to use it · 0ebfff14
      Benjamin Herrenschmidt 提交于
      This adds the new irq remapper core and removes the old one.  Because
      there are some fundamental conflicts with the old code, like the value
      of NO_IRQ which I'm now setting to 0 (as per discussions with Linus),
      etc..., this commit also changes the relevant platform and driver code
      over to use the new remapper (so as not to cause difficulties later
      in bisecting).
      
      This patch removes the old pre-parsing of the open firmware interrupt
      tree along with all the bogus assumptions it made to try to renumber
      interrupts according to the platform. This is all to be handled by the
      new code now.
      
      For the pSeries XICS interrupt controller, a single remapper host is
      created for the whole machine regardless of how many interrupt
      presentation and source controllers are found, and it's set to match
      any device node that isn't a 8259.  That works fine on pSeries and
      avoids having to deal with some of the complexities of split source
      controllers vs. presentation controllers in the pSeries device trees.
      
      The powerpc i8259 PIC driver now always requests the legacy interrupt
      range. It also has the feature of being able to match any device node
      (including NULL) if passed no device node as an input. That will help
      porting over platforms with broken device-trees like Pegasos who don't
      have a proper interrupt tree.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      0ebfff14
  6. 28 6月, 2006 1 次提交
  7. 22 4月, 2006 1 次提交
  8. 24 2月, 2006 1 次提交
  9. 15 1月, 2006 1 次提交
  10. 16 11月, 2005 1 次提交
    • B
      [PATCH] powerpc: pci_64 fixes & cleanups · b5166cc2
      Benjamin Herrenschmidt 提交于
      I discovered that in some cases (PowerMac for example) we wouldn't
      properly map the PCI IO space on recent kernels. In addition, the code
      for initializing PCI host bridges was scattered all over the place with
      some duplication between platforms.
      
      This patch fixes the problem and does a small cleanup by creating a
      pcibios_alloc_controller() in pci_64.c that is similar to the one in
      pci_32.c (just takes an additional device node argument) that takes care
      of all the grunt allocation and initialisation work. It should work for
      both boot time and dynamically allocated PHBs.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      b5166cc2
  11. 10 11月, 2005 1 次提交
    • B
      [PATCH] ppc64: fix PCI IO mapping · 0f34f490
      Benjamin Herrenschmidt 提交于
      phbs_remap_io(), which maps the PCI IO space into the kernel virtual space,
      is called too early on powermac, and thus doesn't work.
      
      This fixes it by removing the call from all platforms and putting it back
      into the ppc64 common code where it belongs, after the actual probing of
      the bus.
      
      That means that before that call, only the ISA IO space (if any) is mapped,
      any PIO access (from quirks for example) will fail. This happens not to be
      a problem for now, but we'll have to rework that code if it becomes one in
      the future.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      0f34f490
  12. 29 10月, 2005 1 次提交
  13. 22 10月, 2005 1 次提交
  14. 20 10月, 2005 1 次提交
  15. 28 9月, 2005 1 次提交
  16. 12 9月, 2005 1 次提交
  17. 09 9月, 2005 1 次提交
    • P
      [PATCH] Separate pci bits out of struct device_node · 1635317f
      Paul Mackerras 提交于
      This patch pulls the PCI-related junk out of struct device_node and
      puts it in a separate structure, struct pci_dn.  The device_node now
      just has a void * pointer in it, which points to a struct pci_dn for
      nodes that represent PCI devices.  It could potentially be used in
      future for device-specific data for other sorts of devices, such as
      virtual I/O devices.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      1635317f
  18. 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