From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: linux-hotplug@vger.kernel.org
Subject: 8/16bit usb minor device number problem
Date: Wed, 27 Sep 2006 09:33:13 +0000 [thread overview]
Message-ID: <451A4559.80109@ciphirelabs.com> (raw)
I have the minor number of usb devices in /dev/bus/usb trunkated.
where do I look for debugging this problem? kernel? filesystem code?
udev? glibc? something else?
foo:/dev/bus/usb/003# ls -l
total 0
crw-rw-r-- 1 root root 189, 0 Sep 26 11:52 001
crw-rw-r-- 1 root root 189, 1 Sep 26 11:52 002
foo:/dev/bus/usb/003# cat /sys/class/usb_device/usbdev3.2/dev
189:257
foo:/dev/bus/usb/003#
no wonder my app fails talking to the device, it was
created with the wrong minor device number.
debian package with backport to sarge:
Version: 0.100-1~bpo.1
udev config:
# usbfs-like devices
SUBSYSTEM="usb_device", PROGRAM="/bin/sh -c 'K=%k;
K=$${K#usbdev}; printf bus/usb/%%03i/%%03i $${K%%%%.*} $${K#*.}'", \
NAME="%c"
for now I can work around it with "rm -rf /dev/bus", but can
someone help me finding the real solution?
Thanks, Andreas
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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-09-27 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 9:33 Andreas Jellinghaus [this message]
2006-09-27 15:22 ` 8/16bit usb minor device number problem Greg KH
2006-09-27 16:03 ` Andreas Jellinghaus
2006-09-27 17:17 ` 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=451A4559.80109@ciphirelabs.com \
--to=aj@ciphirelabs.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).