From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: DEVICE and usb strategy
Date: Mon, 20 Mar 2006 08:04:07 +0000 [thread overview]
Message-ID: <200603200904.08209.aj@dungeon.inka.de> (raw)
In-Reply-To: <dvkfan$9gs$1@sea.gmane.org>
Am Montag, 20. März 2006 02:00 schrieb Kay Sievers:
> Ignore $DEVICE.
...
> Ignore $DEVICE and $INTERFACE entirely and use the values provided by
> the kernel event and the sysfs device pointed to by $DEVPATH.
sorry, that doesn't work. udevmonitor tells me $DEVPATH is always something
that might exist in /sys/ namespace. but I need a device file, something I can
open and use with ioctl() to do my work.
after all why should I be interested in those lower level values, as udev
already does all the work mapping that to a device file name? I'm
only interested in the result: the device name, and of course which
hardware I'm dealing with, so I can start the right driver.
the RUN setting in udev rules: can I only specify my script, or can I use
that setting to pass a parameter to the script, too? if so I could live
without the hardware info and simply the info I need as parameter.
Andreas
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd_______________________________________________
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
prev parent reply other threads:[~2006-03-20 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 20:36 DEVICE and usb strategy Andreas Jellinghaus
2006-03-20 1:00 ` Kay Sievers
2006-03-20 8:04 ` Andreas Jellinghaus [this message]
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=200603200904.08209.aj@dungeon.inka.de \
--to=aj@dungeon.inka.de \
--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).