1. 04 3月, 2011 1 次提交
  2. 15 6月, 2009 1 次提交
  3. 09 6月, 2009 1 次提交
  4. 21 12月, 2008 1 次提交
  5. 20 10月, 2008 1 次提交
  6. 26 9月, 2008 2 次提交
  7. 22 8月, 2008 1 次提交
  8. 09 8月, 2008 1 次提交
  9. 01 7月, 2008 1 次提交
    • L
      [ARM] Orion: make PCI handling code deal with Cardbus slots · da01bba3
      Lennert Buytenhek 提交于
      The Cardbus connector does not have an IDSEL signal, and Cardbus
      cards are always the intended target of configuration transactions
      on their local PCI bus.  This means that if the Orion's PCI bus
      signals are hooked up to a Cardbus slot, the same set of PCI
      functions will will appear 31 times, for each of the PCI device
      IDs 1-31 (ID 0 is the host bridge).
      
      This patch adds a function to the Orion PCI handling code that board
      support code can call to enable Cardbus mode.  When Cardbus mode is
      enabled, configuration transactions on the PCI local bus are only
      allowed to PCI IDs 0 (host bridge) and 1 (cardbus device).
      Signed-off-by: NLennert Buytenhek <buytenh@marvell.com>
      da01bba3
  10. 23 6月, 2008 2 次提交
  11. 09 5月, 2008 1 次提交
  12. 29 4月, 2008 1 次提交
    • L
      [ARM] Orion: fix ->map_irq() PCIe bus number check · 92b913b0
      Lennert Buytenhek 提交于
      The current orion5x board ->map_irq() routines check whether a
      given bus number lives on the PCIe controller by comparing it with
      the PCIe controller's primary bus number.  This doesn't work in
      case there are multiple buses in the PCIe domain, i.e. if there
      exists a PCIe bridge on the primary PCIe bus.
      
      This patch adds a helper function (orion5x_pci_map_irq()) that
      returns the IRQ number for the given PCI device if that device has
      a hard-wired IRQ, or -1 otherwise, and makes each board's
      ->map_irq() function use this helper function.
      Signed-off-by: NLennert Buytenhek <buytenh@marvell.com>
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      92b913b0
  13. 28 3月, 2008 1 次提交