Do your drivers tie into the existing pci_hotplug core? If so, great,
then your userspace interaction is done.
Do you have a pointer to your driver?
> What SW will call my device insert/device remove routines?
If you use the pci_hotplug core, any userspace program can call them
through pcihpfs.
> Please CC me directly on anty response. By the way I read the PDF file Hot
> Pluggable Devices And The Linux Kernel, but I am still not clear on the
> answerrs to the above questions.
Do you mean this document:
http://www.kroah.com/linux/talks/ols_2001_hotplug_paper/hotplug.ps
? That just details how individual drivers can specify the proper
information so that /sbin/hotplug will load them when hardware that they
support is recognized. It has nothing to do with the pci hotplug core,
for that you might want to take a look at:
http://linuxjournal.com/article.php?sid=5633
but to be honest, that article deals more with how to create a
filesystem for a driver. Hopefully, you can glean some insight into how
the userspace interaction works from it. If you still have questions,
please let me know..
I also have a very dumb program at:
http://www.kroah.com/linux/hotplug/
that can power up and down slots in a pci hotplug system. I have an
even simpler bash script that does the same thing around here somewhere,
if people are interested.
Hope this helps,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/