Ignacio Vazquez-Abrams (ivazquez(a)ivazquez.net) said:
Apparently udev can't see them.
"The first thing you need to do is find a directory somewhere in /sys
that corresponds to your hardware, and includes a file named "dev", as
udevinfo can only work on directories of this type. These directories
are all found under either /sys/block or /sys/class - there is no point
looking anywhere else!"
User-mode drivers don't give the device a block or class designator, and
so udev won't handle them.
Sure it will.
At the end of udev.rules:
ACTION=="add", SUBSYSTEM=="usb", MODALIAS=="*", \
RUN+="/sbin/modprobe $modalias"
This gets run for all usb devices to *try* and load a driver. It's running
before the kernel could know whether or not a driver is kenrel or
userspace.
Perhaps the udev docs need some help.
Bill