LimeSDR-Mini PID is currently the default for all Generic FT601 devices

[martin-zs]

Basically can a support request be made to FTDI for a unique PID (they will provide up to 8) for the LimeSDR-Mini and anything that needs to be updated to new PID be updated e.g.
udev-rules/64-limesuite.rules
src/ConnectionFTDI/FTD3XXLibrary/FTD3XX.h

For additional details see:
https://discourse.myriadrf.org/t/any-ftdii-601q-is-recognized-as-ltd-myriad-rf-limesdr-mini/7383/2

[martin-zs]

I should probably add that an equally valid option is to leave it as is, if it is too much trouble to change the PID of a LimeSDR-Mini. And just accept that at some future date (when usb.ids are updated in packages) that a LimeSDR-Mini will be listed as a "Default FT601 USB device” when people on Linux run "lsusb". Then you would just need to update any documentation that refers to it as being a shown as "Myriad-RF LimeSDR-Mini" under Linux.

The actual request for a block of PID's from FTDI is a very low hurdle. All they are seeking is: Name, Company, Country and an E-Mail Address.

[martin-zs]

I just spotted a problem with changing the PID for windows clients:
Product ID 0x60IF
"Product identification as specified in the idProduct field of the USB Device Descriptor This should match the PID in the Windows installation file (INF). If this parameter is changed, then the corresponding change is required in the INF installation file. NOTE: changes to the INF file will invalidate any driver certification."
( ref: https://ftdichip.com/wp-content/uploads/2020/07/AN_370-FT60X-Configuration-Programmer-User-Guide.pdf ).

[martin-zs]

I requested that the Linux device with VID:0403 PID:601f be called "FT601 32-bit FIFO IC" because that better aligns with everything else that is currently in usb.ids for FTDI hardware that uses the default PID for their products.
(ref https://usb-ids.gowdy.us/read/UD/0403/601f )