From: Jon Smirl <jonsmirl@yahoo.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: implementing hotplug event
Date: Tue, 30 Dec 2003 01:48:51 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107274908415884@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107267522216416@msgid-missing>
--- Greg KH <greg@kroah.com> wrote:
> > Now my userspace app needs to open the newly loaded device driver, how
> > do I reliably find it? I know that it is at /dev/dri/cardX but what if
> > the user is replacing /dev with /udev or /devfs? I know the
> > major/minor I could just mknode in my program too.
>
> To be safe, you can always just read the sysfs "dev" file, and do a
> mknod with that information. Otherwise you could query udev as to what
> it has named your device, but we don't have those hooks in udev just
> yet... someday soon...
I just sent the major/minor to the hotplug event in the environment variables,
it seemed easier than sending out the slot id and finding "dev" in sysfs. Doing
mknod from the user space app seems to be the most reliable scheme.
==Jon Smirl
jonsmirl@yahoo.com
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
-------------------------------------------------------
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-30 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 5:19 implementing hotplug event Jon Smirl
2003-12-30 0:39 ` Greg KH
2003-12-30 1:48 ` Jon Smirl [this message]
2003-12-30 22:43 ` 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-107274908415884@msgid-missing \
--to=jonsmirl@yahoo.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).