From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: udev bug? (I don't think so)
Date: Fri, 14 Jul 2006 19:12:35 +0000 [thread overview]
Message-ID: <e98qb4$gt$1@sea.gmane.org> (raw)
There's a sporadic discussion over on the pilot-link mailing lists about
writing udev rules for Palm Treos (and similar multi-port devices).
When one of these devices is plugged in, the visor driver creates two
USB serial devices; a udev rule which matches the SYSFS{idVendor} and
SYSFS{idProduct} will match both serial devices, and /dev/pilot will end
up linked to whichever USB serial port is processed *last*. The last
serial port processed is not necessarily the device with the higher
kernel number.
Several people on the pilot-link list have stated that this is a udev
bug, but I don't agree. AFAIK, udev provides no assurance as to the
order in which events are processed -- regardless of the order in which
they are generated.
Am I correct?
Thanks!
--
====================================
Ian Pilcher i.pilcher@comcast.net
====================================
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
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:[~2006-07-14 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 19:12 Ian Pilcher [this message]
2006-07-15 2:48 ` udev bug? (I don't think so) Greg KH
2006-07-17 13:42 ` Scott James Remnant
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='e98qb4$gt$1@sea.gmane.org' \
--to=i.pilcher@comcast.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.