| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 18 Feb 2014 10:08:27 +0000 From: Steven Newbury <steve@...wbury.org.uk> To: Yinghai Lu <yinghai@...nel.org> Cc: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: pci-3.14 resource alloc On Fri, 2014-02-14 at 11:11 -0800, Yinghai Lu wrote: > On Fri, Feb 14, 2014 at 7:46 AM, Steven Newbury <steve@...wbury.org.uk> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists