From: Tom H <tomh0665@gmail.com>
Date: Mon, 12 Jul 2010 03:43:02 -0400
>From a filesystem perspective, there is an assumed /sys "in front of" /class/...
OK, thanks. This confirms.
joule:/home/peter# cd /sys/class/ieee1394_protocol
joule:/sys/class/ieee1394_protocol# ls -l
total 0
drwxr-xr-x 3 root root 0 2010-07-05 17:46 raw1394
drwxr-xr-x 3 root root 0 2010-07-12 07:48 video1394-0
After the camera is plugged in, the video1394 module is loaded.
So udevadm should also tell something about /dev/video1394/0.
joule:/home/peter# udevadm info --name=/dev/video1394/0 --attribute-walk
Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/class/ieee1394_protocol/video1394-0':
KERNEL=="video1394-0"
SUBSYSTEM=="ieee1394_protocol"
DRIVER==""
These points in the above strike me as problematic or puzzling.
* syslog reports a ROM CRC error while the
camera was new & Coriander gets a live image.
* syslog reports "Node changed".
* udevadm reports an empty DRIVER.
* syslog reports a GUID but udevadm reports nothing
specific to the device. An example in a Ubuntu
document has BUS=="usb", SYSFS{product}=="TS128MJFLASHA"
and many other attributes.
Any further ideas?
Thanks, ... Peter E.
--
Carnot is down, waiting for installation of NetBSD.
Personal site works; http://members.shaw.ca/peasthope/ .
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 171056556.40006.40159.@heaviside.invalid">http://lists.debian.org/171056556.40006.40159.@heaviside.invalid