Donc le retour de udevinfo :
% udevinfo -a -p /sys/devices/pci0000:00/0000:00:02.0/usb3/3-5
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 '/devices/pci0000:00/0000:00:02.0/usb3/3-5':
KERNEL=="3-5"
SUBSYSTEM=="usb"
DRIVER=="usb"
ATTR{configuration}==""
ATTR{bNumInterfaces}==" 1"
ATTR{bConfigurationValue}=="1"
ATTR{bmAttributes}=="80"
ATTR{bMaxPower}=="100mA"
ATTR{urbnum}=="8"
ATTR{idVendor}=="0e6a"
ATTR{idProduct}=="0101"
ATTR{bcdDevice}=="0510"
ATTR{bDeviceClass}=="00"
ATTR{bDeviceSubClass}=="00"
ATTR{bDeviceProtocol}=="00"
ATTR{bNumConfigurations}=="1"
ATTR{bMaxPacketSize0}=="8"
ATTR{speed}=="1.5"
ATTR{busnum}=="3"
ATTR{devnum}=="14"
ATTR{version}==" 1.10"
ATTR{maxchild}=="0"
ATTR{quirks}=="0x0"
ATTR{authorized}=="1"
ATTR{product}=="USB Bridge"
looking at parent device '/devices/pci0000:00/0000:00:02.0/usb3':
KERNELS=="usb3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{configuration}==""
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bMaxPower}==" 0mA"
ATTRS{urbnum}=="15582"
ATTRS{idVendor}=="1d6b"
ATTRS{idProduct}=="0001"
ATTRS{bcdDevice}=="0206"
ATTRS{bDeviceClass}=="09"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bNumConfigurations}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{speed}=="12"
ATTRS{busnum}=="3"
ATTRS{devnum}=="1"
ATTRS{version}==" 1.10"
ATTRS{maxchild}=="8"
ATTRS{quirks}=="0x0"
ATTRS{authorized}=="1"
ATTRS{manufacturer}=="Linux 2.6.27.21-170.2.56.fc10.x86_64 ohci_hcd"
ATTRS{product}=="OHCI Host Controller"
ATTRS{serial}=="0000:00:02.0"
ATTRS{authorized_default}=="1"
looking at parent device '/devices/pci0000:00/0000:00:02.0':
KERNELS=="0000:00:02.0"
SUBSYSTEMS=="pci"
DRIVERS=="ohci_hcd"
ATTRS{vendor}=="0x10de"
ATTRS{device}=="0x03f1"
ATTRS{subsystem_vendor}=="0x1019"
ATTRS{subsystem_device}=="0x2601"
ATTRS{class}=="0x0c0310"
ATTRS{irq}=="22"
ATTRS{local_cpus}=="00000000,00000003"
ATTRS{local_cpulist}=="0-1"
ATTRS{modalias}=="pci:v000010DEd000003F1sv00001019sd00002601bc0Csc03i10"
ATTRS{numa_node}=="0"
ATTRS{broken_parity_status}=="0"
ATTRS{msi_bus}==""
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Mon /etc/udev/rules.d/10-local.rules :
# VDO USB Docking Station
BUS=="usb", ATTR{idVendor}=="0e6a", ATTR{idProduct}=="0101",SYMLINK+="vdo_docking_station", MODE="0666"
Dans /dev, j'ai :
lrwxrwxrwx 1 root root 15 mai 15 22:14 vdo_docking_station -> bus/usb/003/014
Puis :
# ll /dev/bus/usb/003/014
crw-r--r-- 1 root vboxusers 189, 269 mai 15 22:14 /dev/bus/usb/003/014
Donc le nom a bien été changé mais pas le mode, du coup :
% python driver.py
Traceback (most recent call last):
File "driver.py", line 145, in <module>
DockingStation.setBaudRate(38400)
File "driver.py", line 96, in setBaudRate
self.handle.controlMsg(0x40,0x0C,chr(code),0x5003,0x00F0)
usb.USBError: error sending control message: Operation not permitted
zsh: exit 1 python driver.py
Et en root : it works !
J'ai oublié quelque chose ? Peut-être qu'une autre règle d'udev change le mode ? (si j'ai bien compris le fichier 10-local.rules a autorité sur les autres, vu que c'est classé par ordre alphabétique, ou alors c'est l'inverse ?)
Merci !