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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 28 Apr 2011 18:06:50 -0500
From:	Xianghua Xiao <xiaoxianghua@...il.com>
To:	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: PCIe/PCI rescan for new FPGA devices

I have a FPGA-PCIe device and a FPGA-PCI device that are empty at
kernel boot time, they're only loaded after kernel is up. After I load
FPGA images, "lspci" can not show the device, "echo 1 >
/sys/bus/pci/rescan" also does nothing about it. With a reboot I can
see the devices are allocated correctly though, but I want to avoid
the reboot.

I checked at fakephp(which is to be deprecated) and hotplug/rescan,
none of that worked for this scenario.

Can 'rescan' handle cases like this? or, is there a way that I tell
the kernel to reserve a few BARs somehow in the PCI topology at
bootime so I can "insert" the FPGAs later?

Thanks,
Xianghua
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ