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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1171286217.5438.25.camel@localhost.localdomain>
Date:	Mon, 12 Feb 2007 14:16:57 +0100
From:	Andrea Galbusera <andrea.galbusera@...mware.it>
To:	linux-kernel@...r.kernel.org
Subject: Post-boot PCI device detection

Hi all,

I work on a custom board and I have a PCI realated question. Please
redirect me to a more suitable list if you find the following off-topic.

On my board I have a powerpc and an fpga that I need to configure at
boot: once this is accomplished, the fpga implements a PCI device. At
moment I use a "two stages boot" in order to let the PCI subsystem
correctly detect the new device. More in detail:
1. the system boots up my kernel
2. I configure the fpga through SPI with a suitable init script
3. I reboot the ppc (this does not clear fpga config, of course!)
4. Now the kernel show the PCI device and I can load its driver

This works but has performance issues. Here comes the question... Is
there a more suitable way to let the kernel know about the PCI device
being present on the bus without rebooting the system.
No hardware support is available to any sort of hotplug signaling, since
the fpga will never be removed from the system after boot.

How can I signal PCI that something new is present?
I read Documentation/pci.txt but this does not clarify my dubt.

Thank you in advance for any kind help.


-- 
Andrea Galbusera

-
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