From: "Grischa Stegemann" <gs-ml@gmx.net>
To: linux-hotplug@vger.kernel.org
Subject: udev does not create ttyUSB devices for Visor
Date: Tue, 07 Mar 2006 22:13:40 +0000 [thread overview]
Message-ID: <1469.1141769620@www024.gmx.net> (raw)
I have a Handspring Visor device which is supposed to communicate with my
computer using the usb-serial driver.
My udev version is 056 (Debian stable, Kernel 2.6.15.1) and it fails to
create the appropriate device nodes ttyUSB0 and ttyUSB1. When I hit the
hotsync-button on the cradle the kernel recognizes the device correctly:
localhost kernel: usb 1-2: Handspring Visor now attached to ttyUSB0
localhost kernel: usb 1-2: Handspring Visor now attached to ttyUSB1
The simple udev-rule
KERNEL="ttyUSB[0-9]*", NAME="%k"
should now yield the corresponding devices, but it does not. It is
perfectly ignored by udev and I cannot figure out why. There's no problem
with any other device.
It becomes even weirder (for me) if I create the device-nodes by hand:
mknod /dev/ttyUSB0 c 188 0; mknod /dev/ttyUSB1 c 188 1
Now I can communicate with my Visor. BUT once the hotsync-procedure is
finished, the visor disconnects completely from the computer, the
usb-driver deregisters the device and -guess what!- NOW udev removes the
corresponding ttyUSB-nodes.:(
How comes udev is ignoring the device during registering but removes the
device nodes during deregistering the device?
It also removes them if I have absolutely no rule concerning ttyUSB
at all.
Any suggestion and/or clarification is greatly appretiated.
Grischa
--
"Feel free" mit GMX FreeMail!
Monat für Monat 10 FreeSMS inklusive! http://www.gmx.net
-------------------------------------------------------
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=lnk&kid\x110944&bid$1720&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-03-07 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 22:13 Grischa Stegemann [this message]
2006-03-07 23:07 ` udev does not create ttyUSB devices for Visor Kay Sievers
2006-03-08 0:43 ` Greg KH
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=1469.1141769620@www024.gmx.net \
--to=gs-ml@gmx.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.