On Tue, May 29, 2012 at 5:19 PM, Bjorn Helgaas <bhelg...@google.com> wrote: > On Mon, May 21, 2012 at 11:27 AM, Steven Newbury <st...@snewbury.org.uk> > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 18/05/12 10:08, Yinghai Lu wrote: >>> On Fri, May 18, 2012 at 12:45 AM, Yinghai Lu <ying...@kernel.org> >>> wrote: >>>> On Thu, May 17, 2012 at 9:36 AM, Yinghai Lu <ying...@kernel.org> >>>> wrote: >>>>> On Thu, May 17, 2012 at 5:34 AM, Steven Newbury >>>>> <st...@snewbury.org.uk> wrote: >>>>>> -----BEGIN PGP SIGNED MESSAGE----- Strange, the busn branch >>>>>> is merged with for-pci-res-alloc, but for some reason it >>>>>> isn't working. Only the bridge is detected, not the devices >>>>>> behind it. >>>>> >>>>> Can you post the boot log ? maybe recently reordering patches >>>>> applying sequence break it. >>>> >>>> Never mind, found the problem. >>> >>> updated for-pci-res-alloc branch. please check it. >>> >> Tested and working fine now. > > Can you attach dmesg logs without Yinghai's patches (where I assume it > doesn't work) and with them (where it *does* work) to the bugzilla? I > assume https://bugzilla.kernel.org/show_bug.cgi?id=10461 is still the > relevant report. > > I'm confused because I thought your _CRS showed no apertures above > 4GB, and I'm trying to figure out how Yinghai's patches can help if > that's the case.
Your _CRS *doesn't* show any apertures above 4GB, but you're booting with "pci=nocrs", so we ignore them anyway. Doing hotplug with "pci=nocrs" is not a supportable proposition. Patches that help in the "pci=nocrs" case might be acceptable, but only if there is clearly no risk to the "pci=use_crs" case. _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
