I have 2 video devices LML33 and PV155
$ lspci
06:00.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video
cutting chipset (rev 02)
07:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
07:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
07:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
07:09.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
07:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
07:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
07:0b.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
07:0b.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
$ udevinfo -q path -n /dev/video0
/class/video4linux/video0
$ udevinfo -a -p /class/video4linux/video0
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/video4linux/video0':
KERNEL=="video0"
SUBSYSTEM=="video4linux"
SYSFS{name}=="LML33_0_"
SYSFS{dev}=="81:0"
$ udevinfo -q path -n /dev/video1
no record for 'video1' in database
$ udevinfo -q path -n /dev/video2
no record for 'video2' in database
$ udevinfo -q path -n /dev/video3
no record for 'video3' in database
$ udevinfo -q path -n /dev/video4
no record for 'video4' in database
The problem is sometimes when I boot the LML33 is /dev/video0 and
sometimes /dev/video4
I tried a udev rule
SUBSYSTEM=="video4linux", SYSFS{name}=="LML33_0_",SYMLINK="lml33"
but it doesn't work
What do I need to do to get consistant device naming?
Thanks
Richard Ray
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
