IDs
Quoted 3 lines · you
Ok. Though I'd prefer PRODUCT;UNIQ;PHYS or PHYS;PRODUCT;UNIQ. Because PRODUCT and UNIQ are bound together. UNIQ is only defined to be unique in the PRODUCT class of devices, not globally.
PHYS;PRODUCT;UNIQ is ok for me. It has the (very small) advantage that you can have any character in UNIQ, so you don't need to excape semicolons when you get the string from usb.
Quoted 2 lines
There really is no reason to set the serial number taken from the SAPROM on the PCI device ...
In my old scheme there was no difference between the device itself and its functional units, this is why it was neccessary.
bye...
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 8 lines · Tim Jansen
Quoted 3 lines · you
Ok. Though I'd prefer PRODUCT;UNIQ;PHYS or PHYS;PRODUCT;UNIQ. Because PRODUCT and UNIQ are bound together. UNIQ is only defined to be unique in the PRODUCT class of devices, not globally.
PHYS;PRODUCT;UNIQ is ok for me. It has the (very small) advantage that you can have any character in UNIQ, so you don't need to excape semicolons when you get the string from usb.
Ok.
Quoted 5 lines
Quoted 2 lines
There really is no reason to set the serial number taken from the SAPROM on the PCI device ...
In my old scheme there was no difference between the device itself and its functional units, this is why it was neccessary.
I see. I think this is cleaner design, though.
Signature · 7 lines
Vojtech Pavlik SuSE Labs _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net [email protected] https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel