From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiang Liu Subject: Re: [RFC PATCH v5 4/8] ACPI, PCI: avoid building pci_slot as module Date: Tue, 29 Jan 2013 10:45:04 +0800 Message-ID: <510737B0.40903@huawei.com> References: <1358525267-14268-1-git-send-email-jiang.liu@huawei.com> <1358525267-14268-5-git-send-email-jiang.liu@huawei.com> <3500982.MUDp6kKU3R@vostro.rjw.lan> <51072EDA.2000704@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from szxga02-in.huawei.com ([119.145.14.65]:32868 "EHLO szxga02-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753271Ab3A2Cps (ORCPT ); Mon, 28 Jan 2013 21:45:48 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Yinghai Lu Cc: Bjorn Helgaas , "Rafael J. Wysocki" , Jiang Liu , Kenji Kaneshige , Yijing Wang , linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Greg Kroah-Hartman , ACPI Devel Maling List , Toshi Kani , Myron Stowe On 2013-1-29 10:21, Yinghai Lu wrote: > On Mon, Jan 28, 2013 at 6:07 PM, Jiang Liu wrote: >> Could we use quirk to auto-disable PCIe native hotplug for >> problematic platforms? > > that is some kind of boot command line way? We could negotiate between acpiphp and pciehp if those problematic platforms/chipsets could be identified by DMI info or PCI device ID. > > Yinghai > >