From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Jellinghaus Date: Mon, 20 Mar 2006 08:04:07 +0000 Subject: Re: DEVICE and usb strategy Message-Id: <200603200904.08209.aj@dungeon.inka.de> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Am Montag, 20. M=E4rz 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.=20 after all why should I be interested in those lower level values, as udev=20 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