[lkml]   [2014]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: pci-3.14 resource alloc
On Tue, Feb 18, 2014 at 3:08 AM, Steven Newbury <> wrote:
> 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.

Hi Steven, this is a tangent, but can you collect the complete dmesg
log with "pci=nocrs" and let me know what happens when you *don't* use
"pci=nocrs" (a complete dmesg log there would be useful too, but I
don't know if you can boot without it)? I think Linux *should* be
able to handle 64bit BARs even if the BIOS doesn't.

Please post these as a separate thread so we don't muddle this
conversation with Yinghai.


 \ /
  Last update: 2014-02-18 16:41    [W:0.124 / U:22.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site