1. 28 1月, 2009 1 次提交
  2. 08 1月, 2009 1 次提交
    • K
      PCI: pciehp: add ACPI based slot detection · c9ffa5a5
      Kenji Kaneshige 提交于
      There is a problem that some non hot-pluggable PCIe slots are detected
      as hot-pluggable by pciehp on some platforms. The immediate cause of
      this problem is that hot-plug capable bit in the Slot Capabilities
      register is set even for non hot-pluggable slots on those platforms.
      It seems a BIOS/hardware problem, but we need workaround about that.
      
      Some of those platforms define hot-pluggable PCIe slots on ACPI
      namespace properly, while hot-plug capable bit in the Slot
      Capabilities register is set improperly. So using ACPI namespace
      information in pciehp to detect PCIe hot-pluggable slots would be a
      workaround.
      
      This patch adds 'pciehp_detect_mode' module option. When 'acpi' is
      specified, pciehp uses ACPI namespace information to detect PCIe
      hot-pluggable slots.
      Signed-off-by: NKenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      c9ffa5a5
  3. 02 2月, 2008 1 次提交
  4. 28 6月, 2006 1 次提交
  5. 24 3月, 2006 2 次提交
    • K
      [PATCH] PCI Hotplug: add common acpi functions to core · 783c49fc
      Kristen Accardi 提交于
      shpchprm_acpi.c and pciehprm_acpi.c are nearly identical.  In addition,
      there are functions in both these files that are also in acpiphp_glue.c.
      This patch will remove duplicate functions from shpchp, pciehp, and
      acpiphp and move this functionality to pci_hotplug, as it is not
      hardware specific.  Get rid of shpchprm* and pciehprm* files since they
      are no longer needed.  shpchprm_nonacpi.c and pciehprm_nonacpi.c are
      identical, as well as shpchprm_legacy.c and can be replaced with a
      macro.
      
      This patch also changes acpiphp to use the common hpp code.
      Signed-off-by: NKristen Carlson Accardi <kristen.c.accardi@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      783c49fc
    • K
      [PATCH] acpiphp: add dock event handling · 20416ea5
      Kristen Accardi 提交于
      These patches add generic dock event handling to acpiphp.  If there are
      pci devices that need to be inserted/removed after the dock event, the
      event notification will be handed down to the normal pci hotplug event
      handler in acpiphp so that new bridges/devices can be enumerated.
      
      Because some dock stations do not have pci bridges or pci devices that
      need to be inserted after a dock, acpiphp will remain loaded to handle
      dock events even if no hotpluggable pci slots are discovered.
      
      You probably need to have the pci=assign-busses kernel parameter enabled
      to use these patches, and you may not allow ibm_acpi to handle docking
      notifications and use this patch.
      
      This patch incorporates feedback provided by many.
      Signed-off-by: NKristen Carlson Accardi <kristen.c.accardi@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      20416ea5
  6. 09 9月, 2005 1 次提交
    • J
      [PATCH] PCI Hotplug: rpaphp: Move VIO registration · 5eeb8c63
      John Rose 提交于
      Currently, rpaphp registers Virtual I/O slots as hotplug slots.  The
      only purpose of this registration is to ensure that the VIO subsystem
      is notified of new VIO buses during DLPAR adds.  Similarly, rpaphp
      notifies the VIO subsystem when a VIO bus is DLPAR-removed.  The rpaphp
      module has special case code to fake results for attributes like power,
      adapter status, etc.
      
      The VIO register/unregister functions could just as easily be made from
      the DLPAR module.  This patch moves the VIO registration calls to the
      DLPAR module, and removes the VIO fluff from rpaphp altogether.
      Signed-off-by: NJohn Rose <johnrose@austin.ibm.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      5eeb8c63
  7. 25 8月, 2005 1 次提交
  8. 07 7月, 2005 1 次提交
  9. 28 6月, 2005 1 次提交
  10. 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