2023-06-29, 09:54 AM
Thanks a lot, that was really useful. The udevadm is very verbose but it is what I need because I can get the right attribute where the serials are: ATTRS{serial}=="AQ02Z7EX" and this is also the attribute that the udev rule will use.
The extra problem here was that we were using pyudev to get attributes but tags are not the same as udev tags and they are also different between linux distributions (debian, ubuntu...). So, now we use the udevadm tags which are more consistent.
So, difficult decision to make. The standard says that a serial device must have id vendor, id product and serial but reality is different. Should we penalize those who do things well? If we keep model instead of serial it will not be perfect either because most of the identical devices will also share model. If we go back to serial, most of the GPS devices will have to use port to remember devices when identical devices are present, but more than one GPS is not a normal case.
Now I think that we should go back to serial. Your thoughts?
The extra problem here was that we were using pyudev to get attributes but tags are not the same as udev tags and they are also different between linux distributions (debian, ubuntu...). So, now we use the udevadm tags which are more consistent.
So, difficult decision to make. The standard says that a serial device must have id vendor, id product and serial but reality is different. Should we penalize those who do things well? If we keep model instead of serial it will not be perfect either because most of the identical devices will also share model. If we go back to serial, most of the GPS devices will have to use port to remember devices when identical devices are present, but more than one GPS is not a normal case.
Now I think that we should go back to serial. Your thoughts?