From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:26497 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756252Ab2DZM3J (ORCPT ); Thu, 26 Apr 2012 08:29:09 -0400 Message-ID: <4F993F8F.7060704@redhat.com> Date: Thu, 26 Apr 2012 08:29:03 -0400 From: Prarit Bhargava MIME-Version: 1.0 To: Yinghai Lu CC: Bjorn Helgaas , linux-pci@vger.kernel.org, Jesse Barnes , Matthew Wilcox , Don Dutile , Myron Stowe , James Paradis Subject: Re: [PATCH v1] PCI: work around Stratus ftServer broken PCIe hierarchy References: <20120425233632.12292.32916.stgit@bhelgaas.mtv.corp.google.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-pci-owner@vger.kernel.org List-ID: On 04/25/2012 08:30 PM, Yinghai Lu wrote: > On Wed, Apr 25, 2012 at 4:36 PM, Bjorn Helgaas wrote: >> A PCIe downstream port is a P2P bridge. Its secondary interface is >> a link that should lead only to device 0 (unless ARI is enabled)[1], so >> we don't probe for non-zero device numbers. >> >> Some Stratus ftServer systems have a PCIe downstream port (02:00.0) that >> leads to both an upstream port (03:00.0) and a downstream port (03:01.0), >> and 03:01.0 has important devices below it: >> >> [0000:02]-+-00.0-[0000:03]--+-00.0 >> \-01.0-[0000:xx]--+-[USB] >> \-[NIC] >> >> Previously, we didn't enumerate device 03:01.0, so USB and the network >> didn't work. This patch adds a DMI quirk to scan all device numbers, >> not just 0, below a downstream port. > > is there output for > lspci -vvxxx -s 03:00.0 > lspci -vvxxx -s 03:00.1 > > like to know what is the 03:00.0. [Adding correct email addy for Jim@stratus] Jim, can you provide this output? Thanks, P. > > Thanks > > Yinghai