From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: CALLOUT for dri device
Date: Sat, 27 Dec 2003 21:28:00 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107264145424673@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107254709331645@msgid-missing>
On Sat, Dec 27, 2003 at 01:19:55PM -0800, Jon Smirl wrote:
> That was easy, now it's calling my reset program. How do I tell if it is an
> insert or remove event? My program gets called on both.
Look at the ACTION environment variable.
> Does this work for built-in drivers?
yes.
> Will I get an insert event as soon as userspace is running?
no, the event happens when your device is registered. There is
userspace running very early, look at the initramfs stuff. So you will
probably have to put your application into the initramfs image. People
are working on getting that all working properly.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2003-12-27 21:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 17:26 CALLOUT for dri device Jon Smirl
2003-12-27 19:11 ` Greg KH
2003-12-27 19:11 ` Greg KH
2003-12-27 19:11 ` Greg KH
2003-12-27 19:11 ` Greg KH
2003-12-27 21:19 ` Jon Smirl
2003-12-27 21:28 ` Greg KH [this message]
2003-12-27 22:41 ` Jon Smirl
2003-12-30 0:32 ` Greg KH
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=marc-linux-hotplug-107264145424673@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).