Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 24 Oct 2002 12:33:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 24 Oct 2002 12:33:14 -0400 Received: from momus.sc.intel.com ([143.183.152.8]:17869 "EHLO momus.sc.intel.com") by vger.kernel.org with ESMTP id ; Thu, 24 Oct 2002 12:33:13 -0400 Message-ID: <72B3FD82E303D611BD0100508BB29735046DFF42@orsmsx102.jf.intel.com> From: "Lee, Jung-Ik" To: "'Greg KH'" , "KOCHI, Takayoshi" Cc: "Luck, Tony" , pcihpd-discuss@lists.sourceforge.net, linux-ia64@linuxia64.org, linux-kernel@vger.kernel.org Subject: RE: PCI Hotplug Drivers for 2.5 Date: Thu, 24 Oct 2002 09:37:50 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="ISO-8859-1" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1454 Lines: 35 > > I think we now all agree that resource management should move into a > place where it can be shared by all pci hotplug drivers, right? > > If so, anyone want to propose some common code? I think the stuff in > the ACPI driver that was pulled from the Compaq driver is a > great start. > I can try to pull this into the core myself, but if the Intel > developers > have the time, and energy, I would greatly appreciate their help (or > anyone else who wants to join in.) > Resource Management code in phprm.h works fine for both ACPI based platforms and non-ACPI platforms (smbios, BIOS $HRT, pcibios_pci_irq_routing...) doing php enumeration, configuration, resource allocation, etc. Only phprm_acpi.c is included in this release for size matters. intcphp driver is free from controller type, IA32/IPF, ACPI/non-ACPI and depending on kernel configuration, it can bind to either ACPI PHPRM or non-ACPI PHPRM. PCI resource handling code - that does add/delete/sort/combine, etc on pci_resource - has nothing to do with ACPI or non-ACPI so it should be common across cpqphp, ibmphp, acpiphp and intcphp. They are duplicated and varied due to mother structures differences. > thanks, > > greg k-h > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/