From: Greg KH <greg@kroah.com>
To: "Bloch, Jack" <Jack.Bloch@icn.siemens.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux hot swap support
Date: Tue, 17 Sep 2002 23:50:12 -0700 [thread overview]
Message-ID: <20020918065012.GA6840@kroah.com> (raw)
In-Reply-To: <180577A42806D61189D30008C7E632E8793A60@boca213a.boca.ssc.siemens.com>
On Tue, Sep 17, 2002 at 03:28:17PM -0400, Bloch, Jack wrote:
> I have a cPCI system running a Red Hat 2.4.18-3 Kernel. am running on a
> Pentium III 700Mhz machine, but we have some of our own cPCI HW. I wrote the
> drivers according to the Linux Device Driver 2nd edition (i.e. hot swap
> compliant). But what I am missing is :
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
next prev parent reply other threads:[~2002-09-18 6:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 19:28 Linux hot swap support Bloch, Jack
2002-09-17 21:15 ` Alan Cox
2002-09-18 6:50 ` Greg KH [this message]
[not found] <180577A42806D61189D30008C7E632E8793A64@boca213a.boca.ssc.siemens.com>
2002-09-18 20:37 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-09-18 20:59 Bloch, Jack
2002-09-18 21:05 ` Greg KH
2002-09-18 21:09 Bloch, Jack
2002-09-18 21:30 ` Greg KH
2002-09-18 21:37 Bloch, Jack
2002-09-18 21:47 ` Greg KH
2002-09-19 0:05 ` Scott Murray
2002-09-18 21:51 Bloch, Jack
2002-09-18 22:12 ` Greg KH
2002-09-19 12:19 Bloch, Jack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020918065012.GA6840@kroah.com \
--to=greg@kroah.com \
--cc=Jack.Bloch@icn.siemens.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox