From: "Stephen Morgan" <stephenm@glw.com>
To: linux-hotplug@vger.kernel.org
Subject: getting /dev entries for USB devices
Date: Fri, 22 Apr 2005 16:02:29 +0000 [thread overview]
Message-ID: <NDBBIKDDCLAGMMFDHHDBGEANDAAA.stephenm@glw.com> (raw)
Hello all,
I'm trying to get udev to create nodes for my USB devices. There will be
several of the same device and I need their nodes named according to their
bus location.
I created this rule file in /etc/udev/rules.d, called it 05-aa_dev.rules
BUS="usb", PLACE="1.1", NAME="aa_dev01"
BUS="usb", PLACE="1.2", NAME="aa_dev02"
BUS="usb", PLACE="2.1", NAME="aa_dev03"
BUS="usb", PLACE="2.2", NAME="aa_dev04"
BUS="usb", PLACE="3.1", NAME="aa_dev05"
BUS="usb", PLACE="3.2", NAME="aa_dev06"
BUS="usb", PLACE="4.1", NAME="aa_dev07"
BUS="usb", PLACE="4.2", NAME="aa_dev08"
When I plug the devices in, I see a new entry show up in
/sys/bus/usb/devices, for instance "3-1". In that directory, I can find the
idProduct and idVendor that match my device - so far, so good.
But nothing ever shows up in /dev. I should see one of my device names
appear, shouldn't I?
I've read Daniel Drake's article on writing rules, but I'm sure I could be
missing something.
Thanks for your help.
Stephen Morgan
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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 reply other threads:[~2005-04-22 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 16:02 Stephen Morgan [this message]
2005-04-27 16:18 ` getting /dev entries for USB devices Stephen Morgan
2005-04-28 7:19 ` Kay Sievers
2005-04-28 20:00 ` Stephen Morgan
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=NDBBIKDDCLAGMMFDHHDBGEANDAAA.stephenm@glw.com \
--to=stephenm@glw.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).