From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from know-smtprelay-omc-10.server.virginmedia.net ([80.0.253.74]:47703 "EHLO know-smtprelay-omc-10.server.virginmedia.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755035AbaBRKIc (ORCPT ); Tue, 18 Feb 2014 05:08:32 -0500 Message-ID: <1392718107.15829.12.camel@artifact> Subject: Re: pci-3.14 resource alloc From: Steven Newbury To: Yinghai Lu Cc: "linux-pci@vger.kernel.org" , Linux Kernel Mailing List Date: Tue, 18 Feb 2014 10:08:27 +0000 In-Reply-To: References: <1390773698.3450.12.camel@artifact> <1391643656.1067.1.camel@artifact> <1392392764.3520.11.camel@devel-n900> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-pci-owner@vger.kernel.org List-ID: On Fri, 2014-02-14 at 11:11 -0800, Yinghai Lu wrote: > On Fri, Feb 14, 2014 at 7:46 AM, Steven Newbury wrote: > >> > >> Oh, never mind! I didn't notice pref_bar has been renamed to > >> assign_pref_bars. It's working now! :) > > > > There's no pci bridge/bus hotplug though. Docking doesn't reveal the > > pci-e->pci bridge or the (radeon) devices on the other side. > > oh, no. could be other regression in linus tree or pci/next. > Sorry about taking a while to get back to you. Previously I needed the busn work to get it working, this was included in the resource-alloc branch. It never worked on mainline, the bridge used to show up but never get scanned. Now it's not showing up at all on hotplug. It could be a dock driver regression. > Can you check if linus tree could reveal pci-e->pci bridge? > I'll give it a go. > or do you use iommu/dmar with the system? > No, the only unusual option is I use pci=nocrs since the bios is completely ignorant of support for 64bit BARs. > Thanks > > Yinghai