From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Understanding udevinfo
Date: Sat, 21 Feb 2004 00:39:30 +0000 [thread overview]
Message-ID: <20040221003929.GD18146@kroah.com> (raw)
In-Reply-To: <20040220103858.2f41d3ab@rad1.109bean.org.uk>
On Fri, Feb 20, 2004 at 10:38:58AM +0000, Richard A Downing FBCS wrote:
> I'm trying to get my usbs to work via udev. And I'm finding it very hard to
> understand udevinfo's -p option. For instance: In my /sys filesystem I have a
> directory /sys/bus/usb/devices/1-2. I have it in
> /etc/udev/udev.rules as:
>
> # The ov511 webcam
> BUS="usb", PLACE="1-2", NAME="webcam%n"
>
> and sure enough, in /udev I find a webcam0 with the correct major/minor.
>
> If I type: 'udevinfo -p /sys/bus/usb/devices/1-2 -a' in an attempt to find out
> what else I could put in udev.rules, all I get is:
>
> # udevinfo -p /sys/bus/usb/devices/1-2 -a
> couldn't get the class device
You need to use the /sys/class or /sys/block directory for udevinfo to
be able to give you anything that will work properly.
So for your example, try:
udevinfo -p /sys/class/v4l/video0 -a
or whatever the class directory for your device is at.
Hope this helps,
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&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
prev parent reply other threads:[~2004-02-21 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 10:38 Understanding udevinfo Richard A Downing FBCS
2004-02-21 0:39 ` Greg KH [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=20040221003929.GD18146@kroah.com \
--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).