From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: RE: getting /dev entries for USB devices
Date: Thu, 28 Apr 2005 07:19:03 +0000 [thread overview]
Message-ID: <1114672743.28238.5.camel@localhost.localdomain> (raw)
In-Reply-To: <NDBBIKDDCLAGMMFDHHDBGEANDAAA.stephenm@glw.com>
On Wed, 2005-04-27 at 11:18 -0500, Stephen Morgan wrote:
> > 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?
It depends. Not all devices have device nodes. Some USB devices, like
scanners, are only accessed through usbfs with a userspaces driver.
> Is there a simple way to tell if the .rules file is being applied, I mean,
> other than the nodes appearing in /dev? I've tried intentionally putting
> typos in my file and in 50-udev.rules, but couldn't see that it affected
> anything.
You may run udevtest, with the DEVPATH of this device.
> I don't see a lot of use of PLACE in .rules files, is it working okay?
PLACE is not used anymore and removed from future udev versions. ID
works the same way.
Kay
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
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:[~2005-04-28 7:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 16:02 getting /dev entries for USB devices Stephen Morgan
2005-04-27 16:18 ` Stephen Morgan
2005-04-28 7:19 ` Kay Sievers [this message]
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=1114672743.28238.5.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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